From: serge.hallyn@ubuntu.com
To: linux-kernel@vger.kernel.org
Cc: adityakali@google.com, tj@kernel.org, linux-api@vger.kernel.org,
containers@lists.linux-foundation.org, cgroups@vger.kernel.org,
akpm@linux-foundation.org, ebiederm@xmission.com,
gregkh@linuxfoundation.org, lizefan@huawei.com,
hannes@cmpxchg.org
Subject: Show virtualized dentry root in mountinfo for cgroupfs
Date: Sun, 17 Apr 2016 15:04:30 -0500 [thread overview]
Message-ID: <1460923472-29370-1-git-send-email-serge.hallyn@ubuntu.com> (raw)
With the current cgroup namespace patches, the root dentry path of a
mount as shown in /proc/self/mountinfo is the full global cgroup
path. It is common for userspace to use /proc/self/mountinfo to
search for cgroup mountpoints, and expect the root dentry path to
relate to the cgroup paths in /proc/self/cgroup. Patch 2 in this
set therefore virtualizes the root dentry path relative to the
reader's cgroup namespace root.
Patch 1 fixes a bug in kernfs_path_from_node_locked() which is
exposed by patch 2.
next reply other threads:[~2016-04-17 20:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 20:04 serge.hallyn [this message]
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
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=1460923472-29370-1-git-send-email-serge.hallyn@ubuntu.com \
--to=serge.hallyn@ubuntu.com \
--cc=adityakali@google.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=lizefan@huawei.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
all inboxes | Powered by JetHome®