Date: Wed, 23 Feb 2011 10:23:14 +0100
From: Florian Mickler <florian@mickler.org>
To: Miklos Szeredi <mszeredi@suse.cz>
Cc: Tejun Heo <tj@kernel.org>, viro@zeniv.linux.org.uk,
        linux-kernel@vger.kernel.org, kovariadam@gmail.com
Subject: Re: FUSE triggering BUG through blkdev_put()
Message-ID: <20110223102314.129aac51@schatten.dmk.lab>
In-Reply-To: <1297695340.19726.294.camel@tucsk.pomaz.szeredi.hu>
References: <20110214105659.GB18742@htj.dyndns.org>
	<1297695340.19726.294.camel@tucsk.pomaz.szeredi.hu>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1134
Lines: 33

On Mon, 14 Feb 2011 15:55:40 +0100
Miklos Szeredi <mszeredi@suse.cz> wrote:

> On Mon, 2011-02-14 at 11:56 +0100, Tejun Heo wrote:
> > Please take a look at the following bug.
> > 
> >  https://bugzilla.kernel.org/show_bug.cgi?id=28642
> > 
> > The bug title and description are completely misleading but the
> > problem seems to have been caused by the recent eviction related
> > changes.  FUSE ends up blkdev_put'ting while I_CLEAR is still set on
> > the blkdev's inode triggering BUG_ON() in iput().
> 
> Thanks for forwarding.
> 
> It doesn't look to me that it's related to changes in fuse inode
> eviction.  More likely something from the recent inode locking changes.
> 
> Thanks,
> Miklos
> 

The Fuse Bug has nothing to do with the invisible battery of bug
28642. To avoid confusion, the fuse bug is tracked here:
https://bugzilla.kernel.org/show_bug.cgi?id=29202

Regards,
Flo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/