From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Schwab Subject: Re: [RFC] st_nlink after rmdir() and rename() Date: Thu, 03 Mar 2011 17:17:32 +0100 Message-ID: References: <20110303032454.GI22723@ZenIV.linux.org.uk> <406B4874-D3D8-4C05-9FA5-8A7A18ABF89C@mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Al Viro , Linus Torvalds , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Theodore Tso Return-path: In-Reply-To: <406B4874-D3D8-4C05-9FA5-8A7A18ABF89C@mit.edu> (Theodore Tso's message of "Thu, 3 Mar 2011 09:34:08 -0500") Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Theodore Tso writes: > On Mar 2, 2011, at 10:24 PM, Al Viro wrote: > >> We have an interesting problem. Consider the following sequence >> of syscalls: >> mkdir("foo", 0777); >> mkdir("bar", 0777); >> fd1 = open("foo", O_DIRECTORY); >> fd2 = open("bar", O_DIRECTORY); >> rename("foo", "bar"); /* kill old bar */ > > I must be missing something. I didn't think you could rename on > top of a directory and have the directory disappear. Don't you get > an error in that case? rename is required to be able to move a directory over an empty directory, atomically. > What happens if bar contains files? That's an error. Andreas. -- Andreas Schwab, schwab@redhat.com GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E "And now for something completely different."