On Wed, Jan 18, 2006 at 11:13:41PM +0000, Alan Cox wrote:
> On Mer, 2006-01-18 at 14:09 -0500, Dave Jones wrote:
> > On Wed, Jan 18, 2006 at 03:27:16AM -0800, Andrew Morton wrote:
> >
> > > Well yes, that code is kfree()ing a locked mutex. It's somewhat weird to
> > > take a lock on a still-private object but whatever. The code's legal
> > > enough.
> > >
>
> If someone else can be waiting on it then it doesn't look legal ?
it's allocated in this function, and we only kfree it in an error path
if something goes wrong. If we get to the kfree, the policy has
never been seen anywhere outside of cpufreq_add_dev(), so nothing
else can be waiting on it.
Dave
-
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/
[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]
