public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: umount(/proc) after CLONE_NEWNS in 2.6.25?
Date: Mon, 28 Apr 2008 21:30:13 +0400	[thread overview]
Message-ID: <481609A5.1080905@msgid.tls.msk.ru> (raw)

Since 2.6.25, it isn't possible anymore to umount
/proc after clone(CLONE_NEWNS).  It worked fine
before.  E.g:

# strace newnamespace umount -n /proc

2.6.24:

[pid 30121] clone(child_stack=0xff8c21f4, flags=CLONE_NEWNS|SIGCHLD) = 30122
[pid 30122] execve("/usr/sbin/umount", ["umount", "-n", "/proc"])
...
[pid 30122] oldumount("/proc")          = 0


2.6.25:

[pid 6308] clone(child_stack=0xbfc9de94, flags=CLONE_NEWNS|SIGCHLD) = 6309
[pid  6309] execve("/usr/sbin/umount", ["umount", "-n", "/proc"])
...
[pid  6309] oldumount("/proc")          = -1 EBUSY (Device or resource busy)
umount: /proc: device is busy

Yes, various NAMESPACEs are enabled (i'm trying to experiment with
those).

Is it intentional?

Thanks.

/mjt

             reply	other threads:[~2008-04-28 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 17:30 Michael Tokarev [this message]
2008-04-28 18:27 ` umount(/proc) after CLONE_NEWNS in 2.6.25? 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

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=481609A5.1080905@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox