public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Paire <paire@ri.silicomp.fr>
To: Guest section DW <dwguest@win.tue.nl>,
	Alexander Viro <viro@math.psu.edu>
Cc: Jean-Marc Saffroy <saffroy@ri.silicomp.fr>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] Inconsistent behaviour of rmdir
Date: Mon, 20 Nov 2000 09:32:39 +0100	[thread overview]
Message-ID: <200011200832.JAA19770@mailhost.ri.silicomp.fr> (raw)
In-Reply-To: Your message of Fri, 17 Nov 2000 15:27:31 -0500. <Pine.GSO.4.21.0011171514210.18150-100000@weyl.math.psu.edu>

> 
> On Fri, 17 Nov 2000, Guest section DW wrote:
> 
> > 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.
> [snip]
> 
Then, I don't understand why the EINVAL error condition does not also include
dot-dot as last component.

> > So, it seems that -EINVAL would be a better return value in case LAST_DOT.
> 
> No problems with that... Linus, could you apply the following (cut-and-paste
> alert)?
> 
I think that there is another case where EINVAL (or EBUSY) should be more
relevant than ENOTEMPTY: consider a process invoking 'rmdir("..")' where "."
is empty and its current root directory (just because ".." and "." refer
to the same directory which is actually empty).

Anyway, thanks for your explainations on this special UNIX FS behaviour.
-Eric
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Eric PAIRE
Web  : http://www.ri.silicomp.com/~paire  | Groupe SILICOMP - Research Institute
Email: eric.paire@ri.silicomp.com         | 2, avenue de Vignate
Phone: +33 (0) 476 63 48 71               | F-38610 Gieres
Fax  : +33 (0) 476 51 05 32               | FRANCE

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

  reply	other threads:[~2000-11-20  9:03 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
2000-11-17 20:27   ` Alexander Viro
2000-11-20  8:32     ` Eric Paire [this message]
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=200011200832.JAA19770@mailhost.ri.silicomp.fr \
    --to=paire@ri.silicomp.fr \
    --cc=dwguest@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --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