[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110223102314.129aac51@schatten.dmk.lab>
Date: Wed, 23 Feb 2011 10:23:14 +0100
From: Florian Mickler <florian@...kler.org>
To: Miklos Szeredi <mszeredi@...e.cz>
Cc: Tejun Heo <tj@...nel.org>, viro@...iv.linux.org.uk,
linux-kernel@...r.kernel.org, kovariadam@...il.com
Subject: Re: FUSE triggering BUG through blkdev_put()
On Mon, 14 Feb 2011 15:55:40 +0100
Miklos Szeredi <mszeredi@...e.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@...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