|
Message-ID: <20180717071223.GA29533@gmail.com> Date: Tue, 17 Jul 2018 09:12:23 +0200 From: Ingo Molnar <mingo@...nel.org> To: Alexander Popov <alex.popov@...ux.com> Cc: Kees Cook <keescook@...omium.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Kernel Hardening <kernel-hardening@...ts.openwall.com>, Pax Team <pageexec@...email.hu>, Brad Spengler <spender@...ecurity.net>, Andrew Lutomirski <luto@...nel.org>, Tycho Andersen <tycho@...ho.ws>, Laura Abbott <labbott@...hat.com>, 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>, 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>, Nick Piggin <npiggin@...il.com>, Al Viro <viro@...iv.linux.org.uk>, David Miller <davem@...emloft.net>, dingtianhong <dingtianhong@...wei.com>, David Woodhouse <dwmw@...zon.co.uk>, Josh Poimboeuf <jpoimboe@...hat.com>, Steven Rostedt <rostedt@...dmis.org>, Dominik Brodowski <linux@...inikbrodowski.net>, Jürgen Groß <jgross@...e.com>, 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>, the arch/x86 maintainers <x86@...nel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v14 0/6] Introduce the STACKLEAK feature and a test for it * Alexander Popov <alex.popov@...ux.com> wrote: > > ... which would keep it initialized and wouldn't be racy, right? > > No, this will break the poison search logic. Ok. > > I.e. only the most expensive part of the function, the scanning, would be > > turned off via the sysctl. I submit that this will avoid all measurable > > aspects of the 1% kbuild performance overhead. > > Yes, I've made an experiment - skipping stackleak_erase() cuts almost all > performance penalty of the feature. Ok, that's good! > > A more involved approach can be done in the future if warranted, and the feature > > could be disabled/enabled more thoroughly - but the runtime sysctl would be > > acceptable for me for now, as a first iteration. > > Thanks, I see your point. > I'll return with an additional patch introducing sysctl knob + static key for > one-time disabling of stack erasing. Thank you! I'll have a final review of the patch but I guess it will be fine, so if that's the only change then you can also include my: Acked-by: Ingo Molnar <mingo@...nel.org> ... to not hold the patch up for v4.19, and this can go upstream via Kees's tree? Ingo
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.