|
|
Message-ID: <172bdd35-e9b3-95ca-c1bc-58bd7894483b@redhat.com>
Date: Tue, 26 Jun 2018 17:55:40 -0700
From: Laura Abbott <labbott@...hat.com>
To: Kees Cook <keescook@...omium.org>
Cc: Alexander Popov <alex.popov@...ux.com>,
Kernel Hardening <kernel-hardening@...ts.openwall.com>,
PaX Team <pageexec@...email.hu>, Brad Spengler <spender@...ecurity.net>,
Ingo Molnar <mingo@...nel.org>, Andy Lutomirski <luto@...nel.org>,
Tycho Andersen <tycho@...ho.ws>, 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>, "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>,
Steven Rostedt <rostedt@...dmis.org>,
Dominik Brodowski <linux@...inikbrodowski.net>,
Juergen Gross <jgross@...e.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
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>, X86 ML <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v13 (resend) 2/6] x86/entry: Add STACKLEAK erasing the
kernel stack at the end of syscalls
On 06/26/2018 05:21 PM, Kees Cook wrote:
> On Tue, Jun 26, 2018 at 5:13 PM, Kees Cook <keescook@...omium.org> wrote:
>> The only arch-specific part is current_top_of_stack(), so it seems
>> like just solving current_top_of_stack() and copying on_thread_stack()
>> directly should work, yes? I would think sticking those directly into
>> asm/processor.h on arm64 would be okay?
>
> The difference in the earlier x86 and arm64 erase_kstack was:
>
> x86:
> if (on_thread_stack())
> boundary = current_stack_pointer;
> else
> boundary = current_top_of_stack();
>
> arm64:
> boundary = current_stack_pointer;
>
> If a sane current_top_of_stack() isn't possible on arm64, I'm not
> opposed to a small bit of arch-specific ifdef in there:
>
> boundary = get_stack_boundary();
>
> static inline unsigned long get_stack_boundary(void)
> {
> #ifdef CONFIG_X86
> if (!on_thread_stack())
> return current_top_of_stack();
> #else
> return current_stack_pointer;
> }
>
> -Kees
>
I _think_ I have reasonable implementations for both functions,
I was asking about pulling stuff out into a new header because
I wanted to see about reusing on_task_stack which was defined
in asm/stacktrace.h and I was concerned about include nightmares
with asm/processor.h . I'll see what I come up with.
Thanks,
Laura
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.