From: Guest section DW <dwguest@win.tue.nl>
To: Jean-Marc Saffroy <saffroy@ri.silicomp.fr>,
torvalds@transmeta.com, viro@math.psu.edu,
linux-kernel@vger.kernel.org
Cc: Eric Paire <paire@ri.silicomp.fr>
Subject: Re: [BUG] Inconsistent behaviour of rmdir
Date: Fri, 17 Nov 2000 18:56:38 +0100 [thread overview]
Message-ID: <20001117185638.A8452@win.tue.nl> (raw)
In-Reply-To: <Pine.LNX.4.21.0011161400290.24271-100000@sisley.ri.silicomp.fr>
In-Reply-To: <Pine.LNX.4.21.0011161400290.24271-100000@sisley.ri.silicomp.fr>; from Jean-Marc Saffroy on Thu, Nov 16, 2000 at 02:47:35PM +0100
On Thu, Nov 16, 2000 at 02:47:35PM +0100, Jean-Marc Saffroy wrote:
> As you see, it looks like the rmdir fails simply because the dir name ends
> with a dot !! This is confirmed by sys_rmdir in fs/namei.c, around line
> 1384 :
>
> switch(nd.last_type) {
> case LAST_DOTDOT:
> error = -ENOTEMPTY;
> goto exit1;
> case LAST_ROOT: case LAST_DOT:
> error = -EBUSY;
> goto exit1;
> }
I see that an entire discussion has taken place. Let me just remark this,
quoting the Austin draft:
If the path argument refers to a path whose final component is either
dot or dot-dot, rmdir( ) shall fail.
EINVAL The path argument contains a last component that is dot.
EEXIST or ENOTEMPTY The path argument names a directory that is not an empty directory,
EBUSY The directory to be removed is currently in use by the system or some process
and the implementation considers this to be an error.
So, it seems that -EINVAL would be a better return value in case LAST_DOT.
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-17 18:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 13:47 [BUG] Inconsistent behaviour of rmdir Jean-Marc Saffroy
2000-11-16 15:49 ` Linus Torvalds
2000-11-16 17:49 ` Alexander Viro
2000-11-16 18:14 ` Jean-Marc Saffroy
2000-11-16 18:28 ` Alexander Viro
2000-11-16 18:51 ` Jean-Marc Saffroy
2000-11-16 18:59 ` Alexander Viro
2000-11-16 21:17 ` David Feuer
2000-11-16 22:35 ` H. Peter Anvin
2000-11-16 23:10 ` Alexander Viro
2000-11-16 23:43 ` David Feuer
2000-11-17 0:04 ` Alexander Viro
2000-11-18 1:30 ` Nix
2000-11-18 1:58 ` Alexander Viro
2000-11-17 17:56 ` Guest section DW [this message]
2000-11-17 20:27 ` Alexander Viro
2000-11-20 8:32 ` Eric Paire
2000-11-20 9:39 ` Guest section DW
-- strict thread matches above, loose matches on Subject: below --
2000-11-16 16:07 Jesse Pollard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001117185638.A8452@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=paire@ri.silicomp.fr \
--cc=saffroy@ri.silicomp.fr \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox