lkml.org 
[lkml]   [2000]   [Nov]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [BUG] Inconsistent behaviour of rmdir
Date
From
> 
> 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/

\
 
 \ /
  Last update: 2005-03-22 12:47    [W:0.044 / U:43.088 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site