[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <32BCF7CC-CBE8-45AD-B3D8-2856DD4FFF30@gmail.com>
Date: Tue, 12 Mar 2024 09:20:40 +0200
From: Nadav Amit <nadav.amit@...il.com>
To: Andy Lutomirski <luto@...nel.org>
Cc: Dave Hansen <dave.hansen@...el.com>,
Pasha Tatashin <pasha.tatashin@...een.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
the arch/x86 maintainers <x86@...nel.org>,
Borislav Petkov <bp@...en8.de>,
Christian Brauner <brauner@...nel.org>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Ben Segall <bsegall@...gle.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
dianders@...omium.org,
dietmar.eggemann@....com,
eric.devolder@...cle.com,
Heiko Carstens <hca@...ux.ibm.com>,
"hch@...radead.org" <hch@...radead.org>,
"H. Peter Anvin" <hpa@...or.com>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>,
Jason Gunthorpe <jgg@...pe.ca>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Joerg Roedel <jroedel@...e.de>,
Juri Lelli <juri.lelli@...hat.com>,
Kent Overstreet <kent.overstreet@...ux.dev>,
kinseyho@...gle.com,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Lorenzo Stoakes <lstoakes@...il.com>,
mgorman@...e.de,
mic@...ikod.net,
michael.christie@...cle.com,
Ingo Molnar <mingo@...hat.com>,
mjguzik@...il.com,
"Michael S. Tsirkin" <mst@...hat.com>,
Nicholas Piggin <npiggin@...il.com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Petr Mladek <pmladek@...e.com>,
Rick P Edgecombe <rick.p.edgecombe@...el.com>,
Steven Rostedt <rostedt@...dmis.org>,
Suren Baghdasaryan <surenb@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Uladzislau Rezki <urezki@...il.com>,
vincent.guittot@...aro.org,
Valentin Schneider <vschneid@...hat.com>
Subject: Re: [RFC 11/14] x86: add support for Dynamic Kernel Stacks
> On 12 Mar 2024, at 2:02, Andy Lutomirski <luto@...nel.org> wrote:
>
> Doesn't this buy a new problem? Install a page, run the thread without using the page but speculatively load the PTE as read-only into the TLB, context-switch out the thread, (entirely safely and correctly) determine that the page wasn't used, remove it from the PTE, use it for something else and fill it with things that aren't zero, run the thread again, and read from it. Now it has some other thread's data!
Yes, you are correct. Bad idea of mine. Regardless of data leak, it opens the door for subtle hard-to-analyze bugs where 2 reads return different values.
Powered by blists - more mailing lists