Re: [PATCH] LIB: remove unmatched write_lock() in gen_pool_destroy
From: Jiri Kosina
Date: Tue Jun 16 2009 - 04:23:47 EST
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?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/