[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4hEufFemihN8-pRC1sUqSzC9vbK8_s28Vyacd_e7-muow@mail.gmail.com>
Date: Mon, 23 Apr 2018 06:50:36 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Michal Hocko <mhocko@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [PATCH 0/7] Various Spectre-v1 fixes
On Mon, Apr 23, 2018 at 2:33 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> 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 :-)
+1 from me for -stable.
Powered by blists - more mailing lists