linux-kernel - Re: [PATCH 0/7] Various Spectre-v1 fixes

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]

Message-ID: <20180423093321.GV4064@hirez.programming.kicks-ass.net>
Date:   Mon, 23 Apr 2018 11:33:21 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Michal Hocko <mhocko@...nel.org>
Cc:     linux-kernel@...r.kernel.org, mingo@...nel.org, tglx@...utronix.de,
        dan.j.williams@...el.com, torvalds@...ux-foundation.org,
        Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [PATCH 0/7] Various Spectre-v1 fixes

On Sun, Apr 22, 2018 at 07:03:44PM -0600, Michal Hocko wrote:
> On Fri 20-04-18 15:14:07, Peter Zijlstra wrote:
> > These fix a number of perf, x86 and sched cases where we have user controlled
> > array dereferences.  All were found by Dan's recent Smatch update.
> 
> Do we want to mark all of these for stable?

If we all agree that any (speculative) user-controlled array index --
irrespective of the existence of the second load/store that would
complete the gadget -- needs fixing and thus all these patches are
'good', then yes, that makes sense.

Given yours is the only response so far, I suspect we're good on all
that :-)