Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180221100545.GB16426@pd.tnic>
Date: Wed, 21 Feb 2018 11:05:45 +0100
From: Borislav Petkov <bp@...en8.de>
To: Kees Cook <keescook@...omium.org>,
	Alexander Popov <alex.popov@...ux.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Andy Lutomirski <luto@...nel.org>,
	Kernel Hardening <kernel-hardening@...ts.openwall.com>,
	PaX Team <pageexec@...email.hu>,
	Brad Spengler <spender@...ecurity.net>,
	Ingo Molnar <mingo@...nel.org>, Tycho Andersen <tycho@...ho.ws>,
	Laura Abbott <labbott@...hat.com>,
	Mark Rutland <mark.rutland@....com>,
	Ard Biesheuvel <ard.biesheuvel@...aro.org>,
	"H . Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	"Dmitry V . Levin" <ldv@...linux.org>, X86 ML <x86@...nel.org>,
	Mohamed Ghannam <simo.ghannam@...il.com>
Subject: Re: [PATCH RFC v8 0/6] Introduce the STACKLEAK feature and a test
 for it

On Tue, Feb 20, 2018 at 03:17:21PM -0800, Kees Cook wrote:
> On Tue, Feb 20, 2018 at 2:29 AM, Alexander Popov <alex.popov@...ux.com> wrote:
> > On 16.02.2018 21:10, Alexander Popov wrote:
> >> This is the 8th version of the patch series introducing STACKLEAK to the
> >> mainline kernel. I've made some minor improvements while waiting for the
> >> next review by x86 maintainers.
> 
> If we can borrow some of luto or tglx's time, I think that'd be best:

Btw, someone just noticed: why hasn't this patchset ever been sent to
lkml for a wider review?

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

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.