Re: [PATCH 1/2] Don't forget to unlock uids_mutex on error paths

On Wed, Nov 21, 2007 at 01:49:33PM +0300, Pavel Emelyanov wrote:
> The commit
> 
> commit 5cb350baf580017da38199625b7365b1763d7180
> Author: Dhaval Giani <[email protected]>
> Date:   Mon Oct 15 17:00:14 2007 +0200
> 
>     sched: group scheduling, sysfs tunables
> 
> introduced the uids_mutex and the helpers to lock/unlock it.
> Unfortunately, the error paths of alloc_uid() were not patched
> to unlock it.
> 

Thanks for catching it. Looks good to me. Ingo, could you please pick
these up?

> Signed-off-by: Pavel Emelyanov <[email protected]>
Acked-by: Dhaval Giani <[email protected]>

-- 
regards,
Dhaval
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 1/2] Don't forget to unlock uids_mutex on error paths
    • From: Ingo Molnar <[email protected]>

• References:
  • [PATCH 1/2] Don't forget to unlock uids_mutex on error paths
    • From: Pavel Emelyanov <[email protected]>

• Prev by Date: Re: CONFIG_IRQBALANCE for 64-bit x86 ?
• Next by Date: Re: [PATCH 2/2] Merge multiple error paths in alloc_uid into one
• Previous by thread: [PATCH 1/2] Don't forget to unlock uids_mutex on error paths
• Next by thread: Re: [PATCH 1/2] Don't forget to unlock uids_mutex on error paths
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]