From: Peter Zijlstra <peterz@infradead.org>
To: Zefan Li <lizefan@huawei.com>
Cc: Tejun Heo <tj@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Kees Cook <keescook@chromium.org>,
Miao Xie <miaox@cn.fujitsu.com>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] sched: add macros to define bitops for task atomic flags
Date: Tue, 23 Sep 2014 12:01:27 +0200 [thread overview]
Message-ID: <20140923100127.GE3312@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <542124FB.4030109@huawei.com>
On Tue, Sep 23, 2014 at 03:44:59PM +0800, Zefan Li wrote:
> This will simplify code when we add new flags.
>
> v3:
> - Kees pointed out that no_new_privs should never be cleared, so we
> shouldn't define task_clear_no_new_privs(). we define 3 macros instead
> of a single one.
>
> v2:
> - updated scripts/tags.sh, suggested by Peter.
>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Miao Xie <miaox@cn.fujitsu.com>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Signed-off-by: Zefan Li <lizefan@huawei.com>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2014-09-23 10:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 7:44 [PATCH v3 1/3] sched: fix confusing PFA_NO_NEW_PRIVS constant Zefan Li
2014-09-23 7:44 ` [PATCH v3 2/3] sched: add macros to define bitops for task atomic flags Zefan Li
2014-09-23 10:01 ` Peter Zijlstra [this message]
2014-09-23 16:58 ` Kees Cook
2014-09-23 7:45 ` [PATCH v3 3/3] cpuset: PF_SPREAD_PAGE and PF_SPREAD_SLAB should be " Zefan Li
2014-09-23 22:10 ` David Rientjes
2014-09-24 3:15 ` Zefan Li
2014-09-24 13:22 ` [PATCH v3 1/3] sched: fix confusing PFA_NO_NEW_PRIVS constant Tejun Heo
2014-09-24 13:35 ` Tejun Heo
2014-09-24 14:09 ` Tetsuo Handa
2014-09-24 14:32 ` Tejun Heo
2014-09-25 1:42 ` Zefan Li
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=20140923100127.GE3312@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=cgroups@vger.kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=miaox@cn.fujitsu.com \
--cc=mingo@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--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