From: Li Zefan <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: <containers@lists.linux-foundation.org>,
<cgroups@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHSET] cgroup: unexport locking interface
Date: Sun, 7 Apr 2013 13:38:21 +0800 [thread overview]
Message-ID: <5161064D.30000@huawei.com> (raw)
In-Reply-To: <1365118589-10619-1-git-send-email-tj@kernel.org>
On 2013/4/5 7:36, Tejun Heo wrote:
> Hello,
>
> Most cgroup_mutex abuses outside cgroup core proper have been
> eradicated but there's still one use remaining and locking interface
> is still exported. This patchset updates the last user and unexports
> the locking interface and is composed of the following five patches.
>
> 0001-cgroup-cpuset-replace-move_member_tasks_to_cpuset-wi.patch
> 0002-cgroup-relocate-cgroup_lock_live_group-and-cgroup_at.patch
> 0003-cgroup-unexport-locking-interface-and-cgroup_attach_.patch
> 0004-cgroup-kill-cgroup_-un-lock.patch
> 0005-cgroup-remove-cgroup_lock_is_held.patch
>
Acked-by: Li Zefan <lizefan@huawei.com>
next prev parent reply other threads:[~2013-04-07 5:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 23:36 Tejun Heo
2013-04-04 23:36 ` [PATCH 1/5] cgroup, cpuset: replace move_member_tasks_to_cpuset() with cgroup_transfer_tasks() Tejun Heo
2013-04-04 23:36 ` [PATCH 2/5] cgroup: relocate cgroup_lock_live_group() and cgroup_attach_task_all() Tejun Heo
2013-04-04 23:36 ` [PATCH 3/5] cgroup: unexport locking interface and cgroup_attach_task() Tejun Heo
2013-04-04 23:36 ` [PATCH 4/5] cgroup: kill cgroup_[un]lock() Tejun Heo
2013-04-04 23:36 ` [PATCH 5/5] cgroup: remove cgroup_lock_is_held() Tejun Heo
2013-04-07 5:38 ` Li Zefan [this message]
2013-04-07 16:30 ` [PATCHSET] cgroup: unexport locking interface 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=5161064D.30000@huawei.com \
--to=lizefan@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome