[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJcbSZE890YgtEv_Z9A3kPukQzmZmgo0xM=pruMB3uTziBFwMw@mail.gmail.com>
Date: Thu, 31 Jan 2019 14:42:21 -0800
From: Thomas Garnier <thgarnie@...omium.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: Kernel Hardening <kernel-hardening@...ts.openwall.com>, kristen@...ux.intel.com,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>, "the arch/x86 maintainers" <x86@...nel.org>, Jonathan Corbet <corbet@....net>,
Masahiro Yamada <yamada.masahiro@...ionext.com>, Michal Marek <michal.lkml@...kovi.net>,
Herbert Xu <herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net>,
Andy Lutomirski <luto@...nel.org>, Paolo Bonzini <pbonzini@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
Juergen Gross <jgross@...e.com>, Alok Kataria <akataria@...are.com>, Dennis Zhou <dennis@...nel.org>,
Tejun Heo <tj@...nel.org>, Christoph Lameter <cl@...ux.com>, "Rafael J. Wysocki" <rjw@...ysocki.net>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>, Steven Rostedt <rostedt@...dmis.org>,
Joerg Roedel <joro@...tes.org>, Dave Hansen <dave.hansen@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>, Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Stefano Stabellini <sstabellini@...nel.org>, Luis Chamberlain <mcgrof@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Arnd Bergmann <arnd@...db.de>,
Luc Van Oostenryck <luc.vanoostenryck@...il.com>, Jason Baron <jbaron@...mai.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>, Kees Cook <keescook@...omium.org>,
Andrey Ryabinin <aryabinin@...tuozzo.com>, Baoquan He <bhe@...hat.com>,
Alexander Popov <alex.popov@...ux.com>, Jordan Borgner <mail@...dan-borgner.de>,
Nathan Chancellor <natechancellor@...il.com>, Cao jin <caoj.fnst@...fujitsu.com>,
"H.J. Lu" <hjl.tools@...il.com>, Alexey Dobriyan <adobriyan@...il.com>, Nadav Amit <namit@...are.com>,
Yonghong Song <yhs@...com>, Nick Desaulniers <ndesaulniers@...gle.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>, Jann Horn <jannh@...gle.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>, Andrew Morton <akpm@...ux-foundation.org>,
Andi Kleen <ak@...ux.intel.com>, Francis Deslauriers <francis.deslauriers@...icios.com>,
Masami Hiramatsu <mhiramat@...nel.org>, Mimi Zohar <zohar@...ux.ibm.com>,
Nayna Jain <nayna@...ux.ibm.com>, Michael Ellerman <mpe@...erman.id.au>,
Jan Kiszka <jan.kiszka@...mens.com>, Jia Zhang <qianyue.zj@...baba-inc.com>,
Brijesh Singh <brijesh.singh@....com>, Jan Beulich <JBeulich@...e.com>,
Tim Chen <tim.c.chen@...ux.intel.com>, Mike Rapoport <rppt@...ux.vnet.ibm.com>,
Michal Hocko <mhocko@...e.com>, Stephen Rothwell <sfr@...b.auug.org.au>,
Rafael Ávila de Espíndola <rafael@...indo.la>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Nicholas Piggin <npiggin@...il.com>,
Adrian Hunter <adrian.hunter@...el.com>, Song Liu <songliubraving@...com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>, Michael Forney <forney@...gle.com>,
Palmer Dabbelt <palmer@...ive.com>, James Hogan <jhogan@...nel.org>,
Joe Lawrence <joe.lawrence@...hat.com>, nixiaoming <nixiaoming@...wei.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>, linux-kbuild@...r.kernel.org,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>, kvm list <kvm@...r.kernel.org>,
virtualization@...ts.linux-foundation.org,
Linux PM list <linux-pm@...r.kernel.org>, xen-devel <xen-devel@...ts.xenproject.org>,
linux-arch <linux-arch@...r.kernel.org>,
Sparse Mailing-list <linux-sparse@...r.kernel.org>
Subject: Re: [PATCH v6 00/27] x86: PIE support and option to extend KASLR randomization
On Thu, Jan 31, 2019 at 1:41 PM Konrad Rzeszutek Wilk
<konrad.wilk@...cle.com> wrote:
>
> On Thu, Jan 31, 2019 at 11:24:07AM -0800, Thomas Garnier wrote:
> > There has been no major concern in the latest iterations. I am interested on
> > what would be the best way to slowly integrate this patchset upstream.
>
> One question that I was somehow expected in this cover letter - what
> about all those lovely speculative bugs? As in say some one hasn't
> updated their machine with the Spectre v3a microcode - wouldn't they
> be able to get the kernel virtual address space?
Yes they would be.
>
> In effect rendering all this hard-work not needed?
Only if we think Spectre bugs will never be fixed.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
