Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262047AbVDRLwb (ORCPT ); Mon, 18 Apr 2005 07:52:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262045AbVDRLwb (ORCPT ); Mon, 18 Apr 2005 07:52:31 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:51666 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S262047AbVDRLwY (ORCPT ); Mon, 18 Apr 2005 07:52:24 -0400 Date: Mon, 18 Apr 2005 12:52:20 +0100 From: Christoph Hellwig To: "Artem B. Bityuckiy" Cc: Christoph Hellwig , linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, dwmw2@lists.infradead.org Subject: Re: [PATC] small VFS change for JFFS2 Message-ID: <20050418115220.GA22750@infradead.org> Mail-Followup-To: Christoph Hellwig , "Artem B. Bityuckiy" , linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, dwmw2@lists.infradead.org References: <1113814031.31595.3.camel@sauron.oktetlabs.ru> <20050418085121.GA19091@infradead.org> <1113814730.31595.6.camel@sauron.oktetlabs.ru> <20050418105301.GA21878@infradead.org> <1113824781.2125.12.camel@sauron.oktetlabs.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1113824781.2125.12.camel@sauron.oktetlabs.ru> User-Agent: Mutt/1.4.1i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1015 Lines: 19 On Mon, Apr 18, 2005 at 03:46:21PM +0400, Artem B. Bityuckiy wrote: > On Mon, 2005-04-18 at 11:53 +0100, Christoph Hellwig wrote: > > The VFS already has a method for freeing an struct inode pointer, and that > > is ->destroy_inode. You're probably better off updating your GC state from > > that place. > destroy_inode() does not help. JFFS2 already makes use of clear_inode() > which is in fact called even earlier (inode.c from 2.6.11.5, line 298): Oh, I thought the problem is that JFFS2 thought an inode was freed when it still was in use. So you're problem is actually that it's no in the hash anymore but you don't know yet? Anyway, please explain in detail why you need all this information, what errors you see, etc so we can find a way to fix it properly. - 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/