From: Tejun Heo <tj@kernel.org>
To: Li Zefan <lizefan@huawei.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>,
Sasha Levin <sasha.levin@oracle.com>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [PATCH] cpuset: use rcu_read_lock() to protect task_cs()
Date: Mon, 3 Mar 2014 17:31:19 -0500 [thread overview]
Message-ID: <20140303223119.GA26523@mtj.dyndns.org> (raw)
In-Reply-To: <53144223.6000302@huawei.com>
On Mon, Mar 03, 2014 at 04:49:39PM +0800, Li Zefan wrote:
> We no longer use task_lock() to protect tsk->cgroups.
>
> Reported-by: Fengguang Wu <fengguang.wu@intel.com>
> Signed-off-by: Li Zefan <lizefan@huawei.com>
Applied to for-3.15 (do we need this for 3.14-fixes?).
Thanks.
--
tejun
next prev parent reply other threads:[~2014-03-03 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 8:49 Li Zefan
2014-03-03 22:31 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-03 8:49 Li Zefan
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=20140303223119.GA26523@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=sasha.levin@oracle.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®