All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: umount(/proc) after CLONE_NEWNS in 2.6.25?
Date: Tue, 29 Apr 2008 08:36:59 +0400	[thread overview]
Message-ID: <4816A5EB.5090402@msgid.tls.msk.ru> (raw)
In-Reply-To: <20080429021228.GK5882@ZenIV.linux.org.uk>

Al Viro wrote:
> On Tue, Apr 29, 2008 at 03:06:38AM +0100, Al Viro wrote:
> 
>>> Check the version of umount(8) you've got.  And see if that strace happens
>>> to have open of /proc/mounts, without matching close by the time it calls
>>> umount().  util-linux-ng 2.13.1 is _that_ dumb...
>> Umm...  Looks like something more odd is going on...
> 
> ... or something much simpler:
> 
> ; cat /proc/mounts |grep proc
> proc /proc proc rw,nosuid,nodev,noexec 0 0
> usbfs /proc/bus/usb usbfs rw 0 0
> ;
> 
> and unmounting the stuff mounted under /proc before doing umount /proc
> works as expected.  Amazing how well the first cup of coffee helps...

Hey.  Don't paint ME *that* dumb... ;)

It was indeed the case here.  I never tried those things on my
home machine before, and decided to experiment, but I forgot
that it has /proc/bus/usb mounted.  And for comparison I used
another machine which does NOT have that filesystem mounted.
How.. dum^Wodd... ;)

Please excuse me for the noise.

/mj

      reply	other threads:[~2008-04-29  4:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 17:30 umount(/proc) after CLONE_NEWNS in 2.6.25? Michael Tokarev
2008-04-28 18:27 ` Al Viro
2008-04-29  1:47   ` Al Viro
2008-04-29  2:06     ` Al Viro
2008-04-29  2:12       ` Al Viro
2008-04-29  4:36         ` Michael Tokarev [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=4816A5EB.5090402@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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.