From: Jamie Lokier <jamie@shareable.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@osdl.org, viro@parcelfarce.linux.theplanet.co.uk,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] namespace.c: fix bind mount from foreign namespace
Date: Tue, 17 May 2005 02:23:25 +0100 [thread overview]
Message-ID: <20050517012325.GB32226@mail.shareable.org> (raw)
In-Reply-To: <E1DXlcQ-0005h6-00@dorka.pomaz.szeredi.hu>
Miklos Szeredi wrote:
> Bind mount from a foreign namespace results in an un-removable mount.
> The reason is that mnt->mnt_namespace is copied from the old mount in
> clone_mnt(). Because of this check_mnt() in sys_umount() will fail.
>
> The solution is to set mnt->mnt_namespace to current->namespace in
> clone_mnt(). clone_mnt() is either called from do_loopback() or
> copy_tree(). copy_tree() is called from do_loopback() or
> copy_namespace().
>
> When called (directly or indirectly) from do_loopback(), always
> current->namspace is being modified: check_mnt(nd->mnt). So setting
> mnt->mnt_namespace to current->namspace is the right thing to do.
>
> When called from copy_namespace(), the setting of mnt_namespace is
> irrelevant, since mnt_namespace is reset later in that function for
> all copied mounts.
>
> Signed-off-by: Miklos Szeredi <miklos@szeredi.hu>
This patch is correct. The old code was buggy for more fundamental
and serious reason: it broke the invariant that a tree of vfsmnts all
have the same value of mnt_namespace (and the same for the mnt_list
list).
Signed-off-by: Jamie Lokier <jamie@shareable.org>
> Index: linux/fs/namespace.c
> ===================================================================
> --- linux.orig/fs/namespace.c 2005-05-13 12:22:52.000000000 +0200
> +++ linux/fs/namespace.c 2005-05-13 12:32:36.000000000 +0200
> @@ -160,7 +160,7 @@ clone_mnt(struct vfsmount *old, struct d
> mnt->mnt_root = dget(root);
> mnt->mnt_mountpoint = mnt->mnt_root;
> mnt->mnt_parent = mnt;
> - mnt->mnt_namespace = old->mnt_namespace;
> + mnt->mnt_namespace = current->namespace;
>
> /* stick the duplicate mount on the same expiry list
> * as the original if that was on one */
next prev parent reply other threads:[~2005-05-17 1:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 19:51 [PATCH] namespace.c: fix bind mount from foreign namespace Miklos Szeredi
2005-05-17 1:23 ` Jamie Lokier [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-13 10:44 Miklos Szeredi
2005-05-13 16:49 ` Ram
2005-05-13 17:06 ` Al Viro
2005-05-13 17:17 ` Miklos Szeredi
2005-05-13 17:25 ` Al Viro
2005-05-13 17:34 ` Miklos Szeredi
2005-05-13 17:29 ` Ram
2005-05-13 18:40 ` Miklos Szeredi
[not found] ` <1116012287.6248.410.camel@localhost>
[not found] ` <E1DWfqJ-0004eP-00@dorka.pomaz.szeredi.hu>
[not found] ` <1116013840.6248.429.camel@localhost>
2005-05-14 6:11 ` Miklos Szeredi
2005-05-16 15:11 ` Ram
2005-05-16 8:44 ` Miklos Szeredi
2005-05-16 8:59 ` Miklos Szeredi
2005-05-16 11:26 ` Jamie Lokier
2005-05-16 13:23 ` Miklos Szeredi
2005-05-16 11:14 ` Jamie Lokier
2005-05-17 3:50 ` Ram
2005-05-16 20:15 ` Miklos Szeredi
2005-05-17 1:28 ` Jamie Lokier
2005-05-17 5:34 ` Miklos Szeredi
2005-05-17 18:48 ` Ram
2005-05-17 0:00 ` Jamie Lokier
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=20050517012325.GB32226@mail.shareable.org \
--to=jamie@shareable.org \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@parcelfarce.linux.theplanet.co.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).