Commit a2b86f77 authored by Zefan Li's avatar Zefan Li Committed by Tejun Heo

sched: fix confusing PFA_NO_NEW_PRIVS constant

Commit 1d4457f9 ("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: default avatarTetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Acked-by: default avatarKees Cook <keescook@chromium.org>
[ lizf: slightly modified subject and changelog ]
Signed-off-by: default avatarZefan Li <lizefan@huawei.com>
Signed-off-by: default avatarTejun Heo <tj@kernel.org>
parent eb4aec84
...@@ -1957,7 +1957,7 @@ static inline void memalloc_noio_restore(unsigned int flags) ...@@ -1957,7 +1957,7 @@ static inline void memalloc_noio_restore(unsigned int flags)
} }
/* Per-process atomic flags. */ /* Per-process atomic flags. */
#define PFA_NO_NEW_PRIVS 0x00000001 /* May not gain new privileges. */ #define PFA_NO_NEW_PRIVS 0 /* May not gain new privileges. */
static inline bool task_no_new_privs(struct task_struct *p) static inline bool task_no_new_privs(struct task_struct *p)
{ {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment