Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 12 Feb 2018 00:34:55 +0300
From: Alexander Popov <>
To: Kees Cook <>
Cc:, PaX Team <>,
 Brad Spengler <>, Ingo Molnar <>,
 Andy Lutomirski <>, Tycho Andersen <>,
 Laura Abbott <>, Mark Rutland <>,
 Ard Biesheuvel <>, Borislav Petkov <>,
 Thomas Gleixner <>, "H . Peter Anvin" <>,
 Peter Zijlstra <>, "Dmitry V . Levin"
 <>, X86 ML <>,
Subject: Re: [PATCH RFC v7 0/6] Introduce the STACKLEAK feature and a test for

On 15.01.2018 22:59, Kees Cook wrote:
> On Fri, Jan 12, 2018 at 6:19 AM, Alexander Popov <> wrote:
>> This is the 7th version of the patch series introducing STACKLEAK to the
>> mainline kernel. STACKLEAK is a security feature developed by Grsecurity/PaX
>> (kudos to them), which:
>>  - reduces the information that can be revealed through kernel stack leak bugs;
>>  - blocks some uninitialized stack variable attacks (e.g. CVE-2010-2963);
>>  - introduces some runtime checks for kernel stack overflow detection.
> I think this is really looking good.

Hello! May I ask whether dear x86 maintainers think so too?

Best regards,

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.