From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Woodhouse Subject: Re: fishy ->put_inode usage in ntfs Date: Wed, 02 Mar 2005 08:53:28 +0000 Message-ID: <1109753608.19535.12.camel@hades.cambridge.redhat.com> 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> <1109719075.28414.19.camel@baythorne.infradead.org> <1109753018.12379.0.camel@imp.csi.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Christoph Hellwig , ntfs-dev , fsdevel Received: from pentafluge.infradead.org ([213.146.154.40]:7837 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S262226AbVCBIxz (ORCPT ); Wed, 2 Mar 2005 03:53:55 -0500 To: Anton Altaparmakov In-Reply-To: <1109753018.12379.0.camel@imp.csi.cam.ac.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, 2005-03-02 at 08:43 +0000, Anton Altaparmakov wrote: > > 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? > > Is it? I must have missed this discussion. )-: Wasn't that why we backported __wait_on_freeing_inode() to 2.4? -- dwmw2