From: Matthew Wilcox <matthew@wil.cx>
To: Pavel Machek <pavel@ucw.cz>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
serue@us.ibm.com, bfields@fieldses.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
ebiederm@xmission.com, linux-fsdevel@vger.kernel.org
Subject: Re: unprivileged mounts vs. rmdir (was: VFS, NFS security bug? ...)
Date: Thu, 26 Mar 2009 07:14:25 -0600 [thread overview]
Message-ID: <20090326131425.GB8014@parisc-linux.org> (raw)
In-Reply-To: <20090326124338.GA1466@ucw.cz>
On Thu, Mar 26, 2009 at 01:43:38PM +0100, Pavel Machek wrote:
> Well... traditionally if you have an open file or cwd inside mounted
> tree... that blocks unmount, right?
>
> What will you do with processes that have open (deleted) files inside
> the mount? What about cwd?
umount -l ?
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-03-26 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f44001920903110553t52ce0ba7l4ba97213e1c51873@mail.gmail.com>
2009-03-12 11:46 ` VFS, NFS security bug? Should CAP_MKNOD and CAP_LINUX_IMMUTABLE be added to CAP_FS_MASK? Igor Zhbanov
[not found] ` <20090311232356.GP13540@fieldses.org>
[not found] ` <20090312161047.GA15209@us.ibm.com>
[not found] ` <517f3f820903121321sf6d2014q8165b925d5d44db7@mail.gmail.com>
[not found] ` <20090313175848.GB27891@fieldses.org>
[not found] ` <cfd18e0f0903141220u66230ceer22ef0cc6aed1d046@mail.gmail.com>
[not found] ` <f44001920903160716i488e3642o869f626a5c3327d0@mail.gmail.com>
[not found] ` <20090316163611.GB10959@fieldses.org>
[not found] ` <20090316170433.GA2996@us.ibm.com>
2009-03-23 13:21 ` unprivileged mounts vs. rmdir (was: VFS, NFS security bug? ...) Miklos Szeredi
2009-03-26 12:43 ` Pavel Machek
2009-03-26 13:14 ` Matthew Wilcox [this message]
2009-03-27 7:04 ` Eric W. Biederman
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=20090326131425.GB8014@parisc-linux.org \
--to=matthew@wil.cx \
--cc=bfields@fieldses.org \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=pavel@ucw.cz \
--cc=serue@us.ibm.com \
--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 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).