From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Woodhouse <dwmw2@infradead.org>
Subject: Re: fishy ->put_inode usage in ntfs
Date: Tue, 01 Mar 2005 23:17:55 +0000
Message-ID: <1109719075.28414.19.camel@baythorne.infradead.org>
References: <20041014112607.GA24508@lst.de>
	 <1097757569.21275.40.camel@imp.csi.cam.ac.uk>
	 <20041014125933.GA26021@lst.de>
	 <1097760404.21275.52.camel@imp.csi.cam.ac.uk>
	 <20050210104719.GA2771@lst.de> <1108046439.12000.9.camel@imp.csi.cam.ac.uk>
	 <20050210144254.GA7222@lst.de>
	 <1108046906.12000.16.camel@imp.csi.cam.ac.uk>
	 <20050210145003.GA7399@lst.de>
	 <1108047572.12000.24.camel@imp.csi.cam.ac.uk>
	 <20050213163512.GA3686@lst.de>
	 <Pine.LNX.4.60.0502142019001.4269@hermes-1.csi.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Cc: Christoph Hellwig <hch@lst.de>,
	ntfs-dev <linux-ntfs-dev@lists.sourceforge.net>,
	fsdevel <linux-fsdevel@vger.kernel.org>
Received: from baythorne.infradead.org ([81.187.226.107]:24001 "EHLO
	baythorne.infradead.org") by vger.kernel.org with ESMTP
	id S262110AbVCAXR6 (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 1 Mar 2005 18:17:58 -0500
To: Anton Altaparmakov <aia21@cam.ac.uk>
In-Reply-To: <Pine.LNX.4.60.0502142019001.4269@hermes-1.csi.cam.ac.uk>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Mon, 2005-02-14 at 20:44 +0000, Anton Altaparmakov wrote:
> So every time we get a concurrent clear_inode() and iget() for the same 
> inode what happens?  We get your "Failed to get bitmap attribute." every 
> time?  Or can clear_inode only be called once the inode is removed from 
> icache? 

I thought we declared that the concurrent clear_inode() and read_inode()
were a VFS bug, and fixed it? It's even fixed in 2.4 now isn't it?

-- 
dwmw2