From: Ram Pai <linuxram@us.ibm.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 7/7] vfs: mountinfo: show dominating group id
Date: Sun, 30 Mar 2008 11:51:57 -0700 [thread overview]
Message-ID: <1206903118.3694.13.camel@ram.us.ibm.com> (raw)
In-Reply-To: <20080327122400.595798095@szeredi.hu>
On Thu, 2008-03-27 at 13:06 +0100, Miklos Szeredi wrote:
> plain text document attachment (mountinfo_dominator.patch)
> From: Miklos Szeredi <mszeredi@suse.cz>
>
> Show peer group ID of nearest dominating group that has intersection
> with the mount's namespace.
>
> Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
> ---
> Documentation/filesystems/proc.txt | 6 ++++
> fs/namespace.c | 9 +++++-
> fs/pnode.c | 51 +++++++++++++++++++++++++++++++++++++
> fs/pnode.h | 1
> 4 files changed, 65 insertions(+), 2 deletions(-)
>
> Index: vfs-2.6/Documentation/filesystems/proc.txt
> ===================================================================
> --- vfs-2.6.orig/Documentation/filesystems/proc.txt 2008-03-27 12:06:15.000000000 +0100
> +++ vfs-2.6/Documentation/filesystems/proc.txt 2008-03-27 12:06:17.000000000 +0100
> @@ -2374,8 +2374,14 @@ possible optional fields are:
>
> shared:X mount is shared in peer group X
> master:X mount is slave to peer group X
> +propagate_from:X mount is slave and receives propagation from peer group X (*)
> unbindable mount is unbindable
>
> +(*) X is the closest dominant peer group under the process's root. If
> +X is the immediate master of the mount, or if there's no dominant peer
> +group under the same root, then only the "master:X" field is present
> +and not the "propagate_from:X" field.
> +
> For more information on mount propagation see:
>
> Documentation/filesystems/sharedsubtree.txt
> Index: vfs-2.6/fs/namespace.c
> ===================================================================
> --- vfs-2.6.orig/fs/namespace.c 2008-03-27 12:06:15.000000000 +0100
> +++ vfs-2.6/fs/namespace.c 2008-03-27 12:06:17.000000000 +0100
> @@ -836,8 +836,13 @@ static int show_mountinfo(struct seq_fil
> /* Tagged fields ("foo:X" or "bar") */
> if (IS_MNT_SHARED(mnt))
> seq_printf(m, " shared:%i", mnt->mnt_group_id);
> - if (IS_MNT_SLAVE(mnt))
> - seq_printf(m, " master:%i", mnt->mnt_master->mnt_group_id);
> + if (IS_MNT_SLAVE(mnt)) {
> + int master = mnt->mnt_master->mnt_group_id;
> + int dom = get_dominating_id(mnt, &p->root);
> + seq_printf(m, " master:%i", master);
> + if (dom && dom != master)
> + seq_printf(m, " propagate_from:%i", dom);
> + }
> if (IS_MNT_UNBINDABLE(mnt))
> seq_puts(m, " unbindable");
>
> Index: vfs-2.6/fs/pnode.c
> ===================================================================
> --- vfs-2.6.orig/fs/pnode.c 2008-03-27 12:06:10.000000000 +0100
> +++ vfs-2.6/fs/pnode.c 2008-03-27 12:06:17.000000000 +0100
> @@ -28,6 +28,57 @@ static inline struct vfsmount *next_slav
> return list_entry(p->mnt_slave.next, struct vfsmount, mnt_slave);
> }
>
> +/*
> + * Return true if path is reachable from root
> + *
> + * namespace_sem is held, and mnt is attached
> + */
> +static bool is_path_reachable(struct vfsmount *mnt, struct dentry *dentry,
> + const struct path *root)
> +{
> + while (mnt != root->mnt && mnt->mnt_parent != mnt) {
> + dentry = mnt->mnt_mountpoint;
> + mnt = mnt->mnt_parent;
> + }
> + return mnt == root->mnt && is_subdir(dentry, root->dentry);
> +}
This function belongs somewhere else, maybe namespace.c since it has
nothing to do with propagation and is generally provides a useful
service.
RP
next prev parent reply other threads:[~2008-03-30 18:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 12:06 [patch 0/7] vfs: mountinfo (v4) Miklos Szeredi
2008-03-27 12:06 ` [patch 1/7] vfs: mountinfo: add dentry_path() Miklos Szeredi
2008-03-27 12:06 ` [patch 2/7] vfs: mountinfo: add seq_file_root() Miklos Szeredi
2008-03-27 12:06 ` [patch 3/7] vfs: mountinfo: add mount ID Miklos Szeredi
2008-03-27 22:13 ` Al Viro
2008-03-27 12:06 ` [patch 4/7] vfs: mountinfo: add mount peer group ID Miklos Szeredi
2008-03-27 12:06 ` [patch 5/7] vfs: mountinfo: allow using process root Miklos Szeredi
2008-03-28 2:08 ` Al Viro
2008-03-28 8:59 ` Miklos Szeredi
2008-03-27 12:06 ` [patch 6/7] vfs: mountinfo: add /proc/<pid>/mountinfo Miklos Szeredi
2008-03-27 22:36 ` Al Viro
2008-03-28 8:48 ` Miklos Szeredi
2008-03-27 12:06 ` [patch 7/7] vfs: mountinfo: show dominating group id Miklos Szeredi
2008-03-27 22:42 ` Al Viro
2008-03-28 8:52 ` Miklos Szeredi
2008-03-30 18:51 ` Ram Pai [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-26 21:11 [patch 0/7] vfs: mountinfo (v3) Miklos Szeredi
2008-03-26 21:11 ` [patch 7/7] vfs: mountinfo: show dominating group id Miklos Szeredi
2008-03-26 22:51 ` Al Viro
2008-03-27 8:34 ` Miklos Szeredi
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=1206903118.3694.13.camel@ram.us.ibm.com \
--to=linuxram@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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).