From: Eric Sandeen Subject: Re: [PATCH] [RFC] remove ext3 inode from orphan list when link and unlink race Date: Fri, 12 Jan 2007 16:01:40 -0600 Message-ID: <45A80544.2030803@redhat.com> References: <45A7F384.3050303@redhat.com> <45A7FA3C.8030209@redhat.com> <45A80213.5060401@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Linux Kernel Mailing List , ext4 development Return-path: Received: from mx1.redhat.com ([66.187.233.31]:44019 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161116AbXALWBx (ORCPT ); Fri, 12 Jan 2007 17:01:53 -0500 To: Alex Tomas In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org Alex Tomas wrote: >>>>>> Eric Sandeen (ES) writes: > ES> I tend to agree, chatting w/ Al I think he does too. :) I'll test > ES> a patch that kicks out ext3_link() with -ENOENT at the top, and resubmit > ES> that if things go well. > > shouldn't VFS do that? Al says "no" and I'm not arguing. :) Apparently this may be OK with some filesystems, and Al says he doesn't want to know about i_nlink in the vfs in any case. But I suppose there may be other filesystems which DO care, and should be checking if they're not. -Eric