Messages in this thread | | | Date | Tue, 16 Jun 2009 10:23:08 +0200 (CEST) | From | Jiri Kosina <> | Subject | Re: [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
| |