From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Serge E. Hallyn" <serge.hallyn@ubuntu.com>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
containers@lists.linux-foundation.org, hannes@cmpxchg.org,
gregkh@linuxfoundation.org, tj@kernel.org,
cgroups@vger.kernel.org, akpm@linux-foundation.org,
serge@hallyn.com
Subject: Re: [PATCH 2/2] mountinfo: implement show_path for kernfs and cgroup
Date: Mon, 18 Apr 2016 20:44:19 -0500 [thread overview]
Message-ID: <20160419014419.GA19080@mail.hallyn.com> (raw)
In-Reply-To: <87mvoqqu48.fsf@x220.int.ebiederm.org>
Quoting Eric W. Biederman (ebiederm@xmission.com):
> "Serge E. Hallyn" <serge.hallyn@ubuntu.com> writes:
>
> >> diff --git a/kernel/cgroup.c b/kernel/cgroup.c
> >> index 671dc05..9a0d7b3 100644
> >> --- a/kernel/cgroup.c
> >> +++ b/kernel/cgroup.c
> >> @@ -1593,6 +1593,40 @@ static int rebind_subsystems(struct cgroup_root *dst_root, u16 ss_mask)
> >> return 0;
> >> }
> >>
> >> +static int cgroup_show_path(struct seq_file *sf, struct kernfs_node *kf_node,
> >> + struct kernfs_root *kf_root)
> >> +{
> >> + int len = 0, ret = 0;
> >> + char *buf = NULL;
> >> + struct cgroup_namespace *ns = current->nsproxy->cgroup_ns;
> >> + struct cgroup_root *kf_cgroot = cgroup_root_from_kf(kf_root);
> >> + struct cgroup *ns_cgroup;
> >> +
> >> + mutex_lock(&cgroup_mutex);
> >
> > Hm, I can't grab the cgroup mutex here because I already have the
> > namespace_sem. But that's required by cset_cgroup_from_root(). Can
> > I just call that under rcu_read_lock() instead? (Not without
> > changing the lockdep_assert_help()). Is there another way to get the
> > info needed here?
>
> Do we need the current cgroup namespace information at all?
>
> Could we not get the relevant cgroup namespace from the mount of
> cgroupfs?
I don't think so. That was my first inclination. But at show_path()
all we have is the vfsmunt->mnt_root. Since all cgroup namespaces
for a hierarchy share the same dentry tree and superblock, there's
no way to tell where the mount's namespace root is supposed to be.
whether we did
# enter new cgroup namespace rooted at cgroup /user.slice/user-1000.slice
mount -t cgroup -o freezer freezer /mnt
or
mount --bind /sys/fs/cgroup/freezer/user.slice/user-1000.slice /mnt
the mountinfo entry will be the same.
> In general the better path is not to have the contents of files depend on
> who is reading the file.
-serge
next prev parent reply other threads:[~2016-04-19 1:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 20:04 Show virtualized dentry root in mountinfo for cgroupfs serge.hallyn
2016-04-17 20:04 ` [PATCH 1/2] kernfs_path_from_node_locked: don't overwrite nlen serge.hallyn
2016-04-20 19:43 ` Tejun Heo
2016-05-02 16:32 ` Tejun Heo
2016-05-02 16:41 ` Greg KH
2016-04-17 20:04 ` [PATCH 2/2] mountinfo: implement show_path for kernfs and cgroup serge.hallyn
2016-04-18 4:11 ` Serge E. Hallyn
2016-04-18 5:29 ` [PATCH 3/2] cgroup_show_path: use a new helper to get current cgns css_set Serge E. Hallyn
2016-04-29 21:42 ` Serge E. Hallyn
2016-05-02 16:35 ` Tejun Heo
2016-05-03 14:26 ` Serge E. Hallyn
2016-04-19 1:12 ` [PATCH 2/2] mountinfo: implement show_path for kernfs and cgroup Eric W. Biederman
2016-04-19 1:44 ` Serge E. Hallyn [this message]
2016-04-19 4:05 ` Serge E. Hallyn
2016-04-26 2:42 ` Serge E. Hallyn
2016-04-26 10:29 ` Karel Zak
2016-04-26 14:36 ` Serge E. Hallyn
2016-05-02 16:33 ` Tejun Heo
2016-05-02 16:34 ` Tejun Heo
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=20160419014419.GA19080@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serge.hallyn@ubuntu.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).