From: Al Viro <viro@ZenIV.linux.org.uk>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: umount(/proc) after CLONE_NEWNS in 2.6.25?
Date: Mon, 28 Apr 2008 19:27:59 +0100 [thread overview]
Message-ID: <20080428182759.GF5882@ZenIV.linux.org.uk> (raw)
In-Reply-To: <481609A5.1080905@msgid.tls.msk.ru>
On Mon, Apr 28, 2008 at 09:30:13PM +0400, Michael Tokarev wrote:
> [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?
It's very odd. Could you bisect that down to offending changeset or
at least narrow the things down to -rc<something>? I'm going down right
now, so won't be able to look into that until tonight...
next prev parent reply other threads:[~2008-04-28 18:32 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 [this message]
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=20080428182759.GF5882@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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