|
Message-ID: <CAGXu5jJgmvqWzJ1kbq-zTsmwkcc9FPXgBdT9qf+Hc4tLcLh87w@mail.gmail.com> Date: Thu, 21 Jun 2018 19:07:46 -0700 From: Kees Cook <keescook@...omium.org> To: Ingo Molnar <mingo@...nel.org> Cc: Alexander Popov <alex.popov@...ux.com>, Laura Abbott <labbott@...hat.com>, Kernel Hardening <kernel-hardening@...ts.openwall.com>, PaX Team <pageexec@...email.hu>, Brad Spengler <spender@...ecurity.net>, Andy Lutomirski <luto@...nel.org>, Tycho Andersen <tycho@...ho.ws>, Mark Rutland <mark.rutland@....com>, Ard Biesheuvel <ard.biesheuvel@...aro.org>, Borislav Petkov <bp@...en8.de>, Richard Sandiford <richard.sandiford@....com>, Thomas Gleixner <tglx@...utronix.de>, "H . Peter Anvin" <hpa@...or.com>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, "Dmitry V . Levin" <ldv@...linux.org>, Emese Revfy <re.emese@...il.com>, Jonathan Corbet <corbet@....net>, Andrey Ryabinin <aryabinin@...tuozzo.com>, "Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>, Thomas Garnier <thgarnie@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>, Alexei Starovoitov <ast@...nel.org>, Josef Bacik <jbacik@...com>, Masami Hiramatsu <mhiramat@...nel.org>, Nicholas Piggin <npiggin@...il.com>, Al Viro <viro@...iv.linux.org.uk>, "David S . Miller" <davem@...emloft.net>, Ding Tianhong <dingtianhong@...wei.com>, David Woodhouse <dwmw@...zon.co.uk>, Josh Poimboeuf <jpoimboe@...hat.com>, Steven Rostedt <rostedt@...dmis.org>, Dominik Brodowski <linux@...inikbrodowski.net>, Juergen Gross <jgross@...e.com>, Linus Torvalds <torvalds@...ux-foundation.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Dan Williams <dan.j.williams@...el.com>, Dave Hansen <dave.hansen@...ux.intel.com>, Mathias Krause <minipli@...glemail.com>, Vikas Shivappa <vikas.shivappa@...ux.intel.com>, Kyle Huey <me@...ehuey.com>, Dmitry Safonov <dsafonov@...tuozzo.com>, Will Deacon <will.deacon@....com>, Arnd Bergmann <arnd@...db.de>, Florian Weimer <fweimer@...hat.com>, Boris Lukashev <blukashev@...pervictus.com>, Andrey Konovalov <andreyknvl@...gle.com>, X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v13 0/6] Introduce the STACKLEAK feature and a test for it On Thu, Jun 21, 2018 at 6:33 PM, Ingo Molnar <mingo@...nel.org> wrote: > > * Kees Cook <keescook@...omium.org> wrote: > >> On Sun, May 27, 2018 at 7:57 AM, Kees Cook <keescook@...omium.org> wrote: >> > On Sat, May 26, 2018 at 1:10 PM, Alexander Popov <alex.popov@...ux.com> wrote: >> >> This is the 13th version of the patch series introducing STACKLEAK to the >> >> mainline kernel for x86. This version comes with style changes according to >> >> the feedback from Ingo Molnar. Previous version discussion: >> >> http://www.openwall.com/lists/kernel-hardening/2018/05/16/1 >> > >> > Thanks for the update! I've pushed it to my tree for 0-day testing: >> > https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=kspp/gcc-plugin/stackleak-v13 >> >> 0-day has been happy with this tree, and with Ingo's freedback >> addressed, I'd like to push this to -next after -rc2 is released (in >> theory this coming Sunday). It needed some rebasing to -rc1, but it >> was all trivial stuff in Kconfg and Makefile from the kbuild tree's >> changes. >> >> Ingo, how do things look to you now? > > don't know: > > triton:~/tip> git fetch "https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=kspp/gcc-plugin/stackleak-v13" > fatal: repository 'https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=kspp/gcc-plugin/stackleak-v13/' not found That's the gitweb URL. It's the kspp/gcc-plugin/stackleak-v13 branch from https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git > How many patches are in there, and how clean is the series? I.e. it would be nice > to have another submission (assuming it's a clean series with not too many > patches). It needs rebasing to -rc1 (which I've done already, but I'm still doing build tests on it). -Kees -- Kees Cook Pixel Security
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.