From: Greg KH <gregkh@linuxfoundation.org>
To: chaixianping@huawei.com
Cc: lizefan@huawei.com, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Zhenghua Jia <jiazhenghua@huawei.com>,
Leeyou <leeyou.li@huawei.com>, Lei Liu <liulei@huawei.com>
Subject: Re: [PATCH] Cgroup:Fix race between fork and update cpuset mask
Date: Fri, 5 Aug 2016 12:49:22 +0200 [thread overview]
Message-ID: <20160805104922.GA857@kroah.com> (raw)
In-Reply-To: <1470309783-11328-1-git-send-email-chaixianping@huawei.com>
On Thu, Aug 04, 2016 at 07:23:03PM +0800, chaixianping@huawei.com wrote:
> From: chaixianping <chaixianping@huawei.com>
>
> Fix the race between fork and update_cpumask or update_nodemask.
> Scenario as follows:
> 1)A process fork a child process, the child process have
> inherited the parent process cpus_allowed,mems_allowed
> Before being added cset->tasks list.
> 2)Update_cpumask or update_nodemask change the parent's allowed
> to a new value, *but the child still is the old value.
> after being added cset->tasks list.
>
> Signed-off-by: Xianping Chai <chaixianping@huawei.com>
This name doesn't match your From: line :(
> Signed-off-by: Zhenghua Jia <jiazhenghua@huawei.com>
> Signed-off-by: Leeyou <leeyou.li@huawei.com>
> Signed-off-by: Lei Liu <liulei@huawei.com>
> ---
> kernel/cpuset.c | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2016-08-05 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 11:23 [PATCH] Cgroup:Fix race between fork and update cpuset mask chaixianping
2016-08-04 11:23 ` chaixianping
2016-08-05 10:49 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-03 11:50 chaixianping
2016-08-03 11:50 ` chaixianping
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=20160805104922.GA857@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chaixianping@huawei.com \
--cc=jiazhenghua@huawei.com \
--cc=leeyou.li@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liulei@huawei.com \
--cc=lizefan@huawei.com \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.