All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Levon <moz@compsoc.man.ac.uk>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]Fix bug:rmdir could remove current working directory
Date: Thu, 11 Oct 2001 00:36:02 +0100	[thread overview]
Message-ID: <20011011003602.B84467@compsoc.man.ac.uk> (raw)
In-Reply-To: <3BC4E8AD.72F175E3@us.ibm.com> <Pine.GSO.4.33.0110101816320.22872-100000@sweetums.bluetronic.net>
In-Reply-To: <Pine.GSO.4.33.0110101816320.22872-100000@sweetums.bluetronic.net>

On Wed, Oct 10, 2001 at 06:21:01PM -0400, Ricky Beam wrote:

> On Wed, 10 Oct 2001, Mingming cao wrote:
> >I read the man page of
> >rmdir(2).  It says in this case EBUSY error should be returned.  I
> >suspected this is a bug and added a check in vfs_rmdir(). The following
> >patch is against 2.4.10 and has been verified.  Please comment and
> >apply.
> 
> The bug is in the manpage.  This was discussed over a year ago (some time

Well, the manpage only states what certain error nr. returns may mean, not what
will be returned when. Do you have an improvement on :

       EBUSY  pathname is the current working directory or root directory of some process.

regards
john

-- 
"Beware of bugs in the above code; I have only proved it correct, not tried
it."
	- Donald Knuth

      reply	other threads:[~2001-10-10 23:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11  0:32 [PATCH]Fix bug:rmdir could remove current working directory Mingming cao
2001-10-10 21:45 ` Alexander Viro
2001-10-11  1:03   ` Mingming cao
2001-10-10 22:09     ` Alexander Viro
2001-10-10 23:17     ` Linus Torvalds
     [not found]     ` <200110102317.f9ANHjN03120@penguin.transmeta.com>
2001-10-11  3:02       ` Mingming cao
2001-10-10 22:21 ` Ricky Beam
2001-10-10 23:36   ` John Levon [this message]

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=20011011003602.B84467@compsoc.man.ac.uk \
    --to=moz@compsoc.man.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.