Re: [PATCH v3 1/3] sched: fix confusing PFA_NO_NEW_PRIVS constant

[Tejun Heo]

On Wed, Sep 24, 2014 at 09:22:18AM -0400, Tejun Heo wrote:
> On Tue, Sep 23, 2014 at 03:44:19PM +0800, Zefan Li wrote:
> > From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
> > 
> > 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@xxxxxxxxxxxxx>
> > Cc: Ingo Molnar <mingo@xxxxxxxxxx>
> > Cc: Miao Xie <miaox@xxxxxxxxxxxxxx>
> > Cc: Kees Cook <keescook@xxxxxxxxxxxx>
> > Signed-off-by: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
> > Acked-by: Kees Cook <keescook@xxxxxxxxxxxx>
> > [ lizf: slightly modified subject and changelog ]
> > Signed-off-by: Zefan Li <lizefan@xxxxxxxxxx>
> 
> 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. :(

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/