[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100607064412.GK31073@ZenIV.linux.org.uk>
Date: Mon, 7 Jun 2010 07:44:12 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Jari Ruusu <jariruusu@...rs.sourceforge.net>
Cc: linux-kernel@...r.kernel.org,
Rusty Russell <rusty@...tcorp.com.au>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: 2.6.35-rc2 module reference counting broken
On Mon, Jun 07, 2010 at 08:20:30AM +0300, Jari Ruusu wrote:
> Someone broke block device module reference counting. Problem occours when a
> modular block device is mounted and unmounted. Not when it is directly read.
> 2.6.34 kernel works OK, but 2.6.35-rc2 kernel seems to increase usage count
> by one for each mount + umount pair.
Very interesting... Looks like mount() bumps refcount by 2. umount() after
that drops refcount by 1, so it's not leaking superblocks.
Which probably means that open_bdev_exclusive() is fscked. Interesting...
FWIW, quick look through the history seems to point to this:
commit 6b4517a7913a09d3259bb1d21c9cb300f12294bd
Author: Tejun Heo <tj@...nel.org>
Date: Wed Apr 7 18:53:59 2010 +0900
block: implement bd_claiming and claiming block
I'm far too sleepy right now, but I'd start with reviewing what that
thing is doing to module refcounting...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists