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.
--
tejun
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
On Mon, 14 Feb 2011 15:55:40 +0100
Miklos Szeredi <[email protected]> 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