Date: Mon, 12 Mar 2018 09:00:51 +0000 From: Ard Biesheuvel <ard.biesheuvel@...aro.org> To: Ingo Molnar <mingo@...nel.org> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Steven Rostedt <rostedt@...dmis.org>, Arnd Bergmann <arnd@...db.de>, Daniel Micay <danielmicay@...il.com>, Kees Cook <keescook@...omium.org>, Dave Hansen <dave.hansen@...ux.intel.com>, Alexander Popov <alex.popov@...ux.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>, Laura Abbott <labbott@...hat.com>, Mark Rutland <mark.rutland@....com>, 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>, Dominik Brodowski <linux@...inikbrodowski.net>, Juergen Gross <jgross@...e.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Dan Williams <dan.j.williams@...el.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>, X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH RFC v9 4/7] x86/entry: Erase kernel stack in syscall_trace_enter() On 12 March 2018 at 08:22, Ingo Molnar <mingo@...nel.org> wrote: > > * Linus Torvalds <torvalds@...ux-foundation.org> wrote: > >> On Tue, Mar 6, 2018 at 1:41 PM, Linus Torvalds >> <torvalds@...ux-foundation.org> wrote: >> > >> > The warning would remain for the case where you don't enable this >> > hardening feature, so it wouldn't go away. >> >> Side note: if in ten years we'd have a minimum gcc version that we >> could just unconditionally say "auto (scalars) initialize to zero", >> then we'd just make that be the *semantics*, and the warning would >> obviously simply not ever be an issue. > > Btw., I'd suggest we initialize aggregate types to zero as well, and then work > from there by marking exceptions via attributes. > I'd argue that we need to move to struct assignment for constructors, similar to how checkpatch recommends it over memcpy()/memset(). That way, the compiler can tell that such a variable is being assigned, and so it can warn in the usual way when it notices a code path that does not involve an initialization. At the same time, it will warn about not returning a value if there is a code path in the constructor that results in no initialization being performed. It should also help the compiler optimize by keeping such variables entirely in registers if the address is never taken otherwise. > From what I've seen over 90% of 'tricky' initialization sequences either don't > matter to performance, or are unnecessarily complicated. > > I.e. let's eliminate VLAs and let's also make the object initialization aspect of > the C language reliably and broadly safe by default (via a GCC plugin) with no > exceptions, and allow an opt-in mechanism for more fragile (but faster if coded > correctly) constructs. > > Is it possible to implement this "safe automatic variable initialization" language > feature via a GCC plugin robustly, while still keeping code generation sane? (i.e. > no forced allocation of stack slots, etc.) It should be a superset of > CONFIG_GCC_PLUGIN_STRUCTLEAK=y. > I think that should be feasible, yes. It would be worth trying whether the current code can be simplified, though: it currently takes care not to add such an initialization if it can already spot one, but I wonder whether just blindly adding one at the start and letting the compiler optimize it away again is safer. > Plugin support is present in GCC version 4.5 and higher, correct? So if such a > plugin is possible we could raise the minimum GCC version to support it > unconditionally. > I think that would be reasonable, yes, but we should check across architectures as well.
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.