[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <159DB397-87E2-435D-9F33-067FF9296ADC@amacapital.net>
Date: Thu, 21 Nov 2019 14:24:21 -0800
From: Andy Lutomirski <luto@...capital.net>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
Fenghua Yu <fenghua.yu@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
H Peter Anvin <hpa@...or.com>,
Ashok Raj <ashok.raj@...el.com>,
Ravi V Shankar <ravi.v.shankar@...el.com>,
linux-kernel <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>
Subject: Re: [PATCH v10 6/6] x86/split_lock: Enable split lock detection by kernel parameter
> On Nov 21, 2019, at 1:51 PM, Luck, Tony <tony.luck@...el.com> wrote:
>
> On Thu, Nov 21, 2019 at 02:15:22PM +0100, Peter Zijlstra wrote:
>> Also, just to remind everyone why we really want this. Split lock is a
>> potent, unprivileged, DoS vector.
>
> So how much do we "really want this"?
>
> It's been 543 days since the first version of this patch was
> posted. We've made exactly zero progress.
>
> Current cut down patch series is the foundation to move one
> small step towards getting this done.
>
> Almost all of what's in this set will be required in whatever
> final solution we want to end up with. Out of this:
Why don’t we beat it into shape and apply it, hidden behind BROKEN. Then we can work on the rest of the patches and have a way to test them.
It would be really, really nice if we could pass this feature through to a VM. Can we?
Powered by blists - more mailing lists