From: Tejun Heo <tj@kernel.org>
To: "Serge E. Hallyn" <serge@hallyn.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,
ebiederm@xmission.com, gregkh@linuxfoundation.org,
cgroups@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 3/2] cgroup_show_path: use a new helper to get current cgns css_set
Date: Mon, 2 May 2016 12:35:26 -0400 [thread overview]
Message-ID: <20160502163526.GW7822@mtj.duckdns.org> (raw)
In-Reply-To: <20160429214254.GA13615@mail.hallyn.com>
On Fri, Apr 29, 2016 at 04:42:54PM -0500, Serge E. Hallyn wrote:
> [ I'm sorry, apparently I had sent the wrong version of this patch. Here
> is the correct one from
> https://git.kernel.org/cgit/linux/kernel/git/sergeh/linux-security.git/commit/?h=2016-04-17/kernfs.show&id=79f784037098fddae92258579ef494537a12f1b2
> Thanks Michael for pointing that out
> ]
>
> Since we're getting current's cgroup namespace info, and are
> not modifying it, we don't need the cgroup_mutex.
>
> Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com>
Can you please fold this into the previous patch?
Thanks.
--
tejun
next prev parent reply other threads:[~2016-05-02 16:35 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 [this message]
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=20160502163526.GW7822@mtj.duckdns.org \
--to=tj@kernel.org \
--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=serge@hallyn.com \
/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®