Re: [PATCH v3 1/3] sched: fix confusing PFA_NO_NEW_PRIVS constant
From: Zefan Li <hidden>
Date: 2014-09-25 01:42:29
Also in:
lkml
From: Zefan Li <hidden>
Date: 2014-09-25 01:42:29
Also in:
lkml
On 2014/9/24 21:35, Tejun Heo wrote:
On Wed, Sep 24, 2014 at 09:22:18AM -0400, Tejun Heo wrote:quoted
On Tue, Sep 23, 2014 at 03:44:19PM +0800, Zefan Li wrote:quoted
From: Tetsuo Handa <penguin-kernel-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org> 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 <redacted> Cc: Ingo Molnar <redacted> Cc: Miao Xie <redacted> Cc: Kees Cook <redacted> Signed-off-by: Tetsuo Handa <penguin-kernel-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org> Acked-by: Kees Cook <redacted> [ lizf: slightly modified subject and changelog ] Signed-off-by: Zefan Li <redacted>Applied 1-3 to cgroup/for-3.17-fixes w/ the typo spotted by davidr fixed.Reverted due to build failure. Will wait for a refreshed version. :(
Didn't notice mm/slab.c uses PF_SPREAD_SLAB without the cpuset wrapper...