9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Alexander Viro <viro@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] [RFC] sysremove()/sysmount() race
Date: Mon,  5 Mar 2001 03:37:34 -0500	[thread overview]
Message-ID: <Pine.GSO.4.21.0103050316310.23684-100000@weyl.math.psu.edu> (raw)

	Folks, AFAICS there is a window during mount() when you
can remove() the mountpoint. There's no locking between namec()
and cmount(), so as far as I can see there's nothing to stop 
sysremove() from happening in that window. Since nothing is mounted
yet, we end up removing the mountpoint (after mount we would attempt
to remove the root of mounted fs).
	I'm not saying that it's a bug, but... how well does userland
deal with that? AFAICS kernel should be OK...
						Cheers,
							Al
PS: ssh'd from a Linux box that runs 2.4.2+namespaces patch. 2 users,
5 different namespaces right now... ;-) Off to porting libfs...



             reply	other threads:[~2001-03-05  8:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-05  8:37 Alexander Viro [this message]
2001-03-05  8:54 Russ Cox

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=Pine.GSO.4.21.0103050316310.23684-100000@weyl.math.psu.edu \
    --to=viro@math.psu.edu \
    --cc=9fans@cse.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;
as well as URLs for NNTP newsgroup(s).