Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261194AbVEFNoo (ORCPT ); Fri, 6 May 2005 09:44:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261187AbVEFNon (ORCPT ); Fri, 6 May 2005 09:44:43 -0400 Received: from [213.170.72.194] ([213.170.72.194]:56806 "EHLO shelob.oktetlabs.ru") by vger.kernel.org with ESMTP id S261172AbVEFNoi (ORCPT ); Fri, 6 May 2005 09:44:38 -0400 Subject: Re: [PATCH] __wait_on_freeing_inode fix From: "Artem B. Bityuckiy" Reply-To: dedekind@infradead.org To: Miklos Szeredi Cc: dwmw2@infradead.org, akpm@osdl.org, wli@holomorphy.com, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org In-Reply-To: References: <1115386405.16187.196.camel@hades.cambridge.redhat.com> Content-Type: text/plain Organization: MTD Date: Fri, 06 May 2005 17:44:32 +0400 Message-Id: <1115387072.27158.31.camel@sauron.oktetlabs.ru> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 638 Lines: 18 > I think it should work without Artem's patch too, since prune_icache() > removes the inode from the hash chain at the same time (under > inode_lock) as changing it's state to I_FREEING. So the pruned inode > will never be seen by iget(). > I suppose this doesn't mean that your patch fixes my problem (it mustn't I believe) ? -- Best Regards, Artem B. Bityuckiy, St.-Petersburg, Russia. - 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/