Subject: Re: FUSE triggering BUG through blkdev_put()
From: Miklos Szeredi <mszeredi@suse.cz>
To: Tejun Heo <tj@kernel.org>
Cc: viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
        kovariadam@gmail.com
In-Reply-To: <20110214105659.GB18742@htj.dyndns.org>
References: <20110214105659.GB18742@htj.dyndns.org>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 14 Feb 2011 15:55:40 +0100
Message-ID: <1297695340.19726.294.camel@tucsk.pomaz.szeredi.hu>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 834
Lines: 23

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

--
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/