From: Alex Tomas Subject: Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race Date: Sat, 13 Jan 2007 00:25:28 +0300 Message-ID: References: <45A7F384.3050303@redhat.com> <45A7FA3C.8030209@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Alex Tomas , Linux Kernel Mailing List , ext4 development Return-path: Received: from fe02.tochka.ru ([62.5.255.22]:46333 "EHLO umail.ru" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1161082AbXALV0p (ORCPT ); Fri, 12 Jan 2007 16:26:45 -0500 To: Eric Sandeen In-Reply-To: <45A7FA3C.8030209@redhat.com> (Eric Sandeen's message of "Fri\, 12 Jan 2007 15\:14\:36 -0600") Sender: linux-ext4-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org >>>>> Eric Sandeen (ES) writes: ES> so I think it's possible that link can sneak in there & find it after ES> the mutex is dropped...? Is this ok? :) It's certainly -happening- ES> anyway.... yes, but it shouldn't allow to re-link such inode back, IMHO. a filesystem may start some non-revertable activity in its unlink method. thanks, Alex