linux-kernel - Re: [PATCH] sched: Do not bug in __sched

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 19 Nov 2018 17:24:32 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Florian Fainelli <f.fainelli@...il.com>,
        Peter Zijlstra <peterz@...radead.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Laurent Dufour <ldufour@...ux.vnet.ibm.com>,
        Andrew Morton <akpm@...l.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] sched: Do not bug in __sched_setscheduler() when pi is
 not used

On Mon, Nov 19, 2018 at 10:46:54AM -0500, Steven Rostedt wrote:
> On Mon, 19 Nov 2018 16:13:11 +0100
> Greg KH <gregkh@...uxfoundation.org> wrote:
> 
> > > Can this patch also be applied to the stable trees? The offending commit
> > > was first introduced in 4.2.  
> > 
> > What is the git commit id of this patch in Linus's tree?
> 
> 896bbb2522587e3b8eb2a0d204d43ccc1042a00d
> 
> The subject was changed when it was applied.

Ah, that helps.

But why is this really needed in the older kernels?  You want to crash
your machine if someone got things wrong?  Given that I doubt this is
being hit anymore, why is it needed in 4.9.y and 4.4.y?

Also, it doesn't apply there so someone needs to do the backport...

thanks,

greg k-h