kernel-hardening - Re: [PATCH v5 14/32] x86/mm/64: Enable vmapped stacks

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160714184527.GB16975@gmail.com>
Date: Thu, 14 Jul 2016 20:45:28 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Andy Lutomirski <luto@...capital.net>
Cc: Andy Lutomirski <luto@...nel.org>, X86 ML <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-arch <linux-arch@...r.kernel.org>,
	Borislav Petkov <bp@...en8.de>, Nadav Amit <nadav.amit@...il.com>,
	Kees Cook <keescook@...omium.org>, Brian Gerst <brgerst@...il.com>,
	"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Josh Poimboeuf <jpoimboe@...hat.com>, Jann Horn <jann@...jh.net>,
	Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: [PATCH v5 14/32] x86/mm/64: Enable vmapped stacks


* Andy Lutomirski <luto@...capital.net> wrote:

> If you think it makes sense, I can split out a bunch of the x86 and mm 
> preparatory patches and, if it reorders cleanly and still works, the 
> THREAD_INFO_IN_TASK thing.  Those could plausibly go in 4.7.  Would
> you like me  to see how that goes?  (I'll verify that it builds, that
> the 0day bot likes it,  and that the final result of the patchset is
> exactly identical to what I already sent.)

Yeah, doing that would be useful - the smaller the riskier bits end up
being the better.

Thanks,

	Ingo

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.