lkml.org 
[lkml]   [2009]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] LIB: remove unmatched write_lock() in gen_pool_destroy
On Mon, 15 Jun 2009, Andrew Morton wrote:

> > > this doesn't really qualify for trivial tree, as it introduces a
> > > significant code change. Adding some CCs.
> > Looks ok to me. Its dumb to aquire the lock you're gonna free anyway.
> > Maybe some BUG_ON() that sez nobody better be holding this lock?
> CONFIG_DEBUG_OBJECTS_FREE could detect the freeing of a held rwlock.
> But probably it hasn't been wired up to handle rwlocks.

Hmm, in fact ... am I just completely blind, or is the only user of
CONFIG_DEBUG_OBJECTS_FREE the timer code?

--
Jiri Kosina
SUSE Labs


\
 
 \ /
  Last update: 2009-06-16 10:27    [W:1.561 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site