Subject: Re: [RFC] st_nlink after rmdir() and rename()
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Theodore Tso <tytso@MIT.EDU>
In-Reply-To: <20110303032454.GI22723@ZenIV.linux.org.uk>
Date: Thu, 3 Mar 2011 09:34:08 -0500
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 7bit
Message-Id: <406B4874-D3D8-4C05-9FA5-8A7A18ABF89C@mit.edu>
References: <20110303032454.GI22723@ZenIV.linux.org.uk>
To: Al Viro <viro@ZenIV.linux.org.uk>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 824
Lines: 26


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?  What happens if bar contains files?

We don't allow:  mkdir("bar", 0777); unlink("bar");

Why should this be any different?

-- Ted

--
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/