sched: fix confusing PFA_NO_NEW_PRIVS constant
authorZefan Li <lizefan@huawei.com>
Thu, 25 Sep 2014 01:40:17 +0000 (09:40 +0800)
committerTejun Heo <tj@kernel.org>
Thu, 25 Sep 2014 02:16:06 +0000 (22:16 -0400)
commita2b86f772227bcaf962c8b134f8d187046ac5f0e
treecb0f90efd0e89cf683210d85441177fe7685d84f
parenteb4aec84d6bdf98d00cedb41c18000f7a31e648a
sched: fix confusing PFA_NO_NEW_PRIVS constant

Commit 1d4457f99928 ("sched: move no_new_privs into new atomic flags")
defined PFA_NO_NEW_PRIVS as hexadecimal value, but it is confusing
because it is used as bit number. Redefine it as decimal bit number.

Note this changes the bit position of PFA_NOW_NEW_PRIVS from 1 to 0.

Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Miao Xie <miaox@cn.fujitsu.com>
Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Acked-by: Kees Cook <keescook@chromium.org>
[ lizf: slightly modified subject and changelog ]
Signed-off-by: Zefan Li <lizefan@huawei.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
include/linux/sched.h