From: Alexander Popov <alex.popov@linux.com>
To: Mark Rutland <mark.rutland@arm.com>, Laura Abbott <labbott@redhat.com>
Cc: Kees Cook <keescook@chromium.org>,
kernel-hardening@lists.openwall.com,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [kernel-hardening] Re: [RFC][PATCH 2/2] arm64: Clear the stack
Date: Wed, 12 Jul 2017 09:01:04 +0300 [thread overview]
Message-ID: <fb9f92d2-6737-d9ae-ed49-fa61a089c727@linux.com> (raw)
In-Reply-To: <20170711195154.GA7124@leverpostej>
Hello Mark,
On 11.07.2017 22:51, Mark Rutland wrote:
> On Mon, Jul 10, 2017 at 03:04:43PM -0700, Laura Abbott wrote:
>> - Where else do we need to clear the stack?
>
> I guess we might need to clear (all of the remainder of) the stack after
> invoking EFI runtime services -- those can run in task context, might
> leave sensitive values on the stack, and they're uninstrumented. The
> same would apply for x86.
Thanks, I've added this to the TODO list.
> I think we can ignore garbage left on the stack by idle/hotplug, since
> that happens in the idle thread, so we shouldn't be doing uaccess
> transfers on those stacks.
Excuse me, I didn't understand what you mean. erase_kstack() is called at the
end of syscall before returning to the userspace.
Best regards,
Alexander
next prev parent reply other threads:[~2017-07-12 6:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 14:30 [kernel-hardening] [PATCH RFC v2 1/1] gcc-plugins: Add stackleak feature erasing the kernel stack at the end of syscalls Alexander Popov
2017-06-09 17:28 ` [kernel-hardening] " Kees Cook
2017-06-09 23:00 ` Alexander Popov
2017-06-20 19:20 ` Kees Cook
2017-06-13 21:51 ` Laura Abbott
2017-06-20 11:20 ` Mark Rutland
2017-06-20 14:13 ` Ard Biesheuvel
2017-06-20 19:11 ` Kees Cook
2017-06-21 9:24 ` Mark Rutland
2017-06-21 15:54 ` Laura Abbott
2017-07-10 22:04 ` [kernel-hardening] [RFC][PATCH 0/2] draft of stack clearing for arm64 Laura Abbott
2017-07-10 22:04 ` [kernel-hardening] [RFC][PATCH 1/2] stackleak: Update " Laura Abbott
2017-07-10 22:04 ` [kernel-hardening] [RFC][PATCH 2/2] arm64: Clear the stack Laura Abbott
2017-07-11 19:51 ` [kernel-hardening] " Mark Rutland
2017-07-11 20:04 ` Mark Rutland
2017-07-12 6:01 ` Alexander Popov [this message]
2017-07-14 20:51 ` Laura Abbott
2017-07-21 16:56 ` Alexander Popov
2017-07-22 0:23 ` Laura Abbott
2017-07-24 8:19 ` Alexander Popov
2017-07-25 3:34 ` Kees Cook
2017-08-18 8:07 ` Alexander Popov
2017-07-11 22:56 ` [kernel-hardening] Re: [RFC][PATCH 0/2] draft of stack clearing for arm64 Alexander Popov
2017-06-23 22:48 ` [kernel-hardening] Re: [PATCH RFC v2 1/1] gcc-plugins: Add stackleak feature erasing the kernel stack at the end of syscalls Tycho Andersen
2017-06-29 21:33 ` Kees Cook
2017-06-29 22:13 ` Tycho Andersen
2017-06-20 9:06 ` [kernel-hardening] " Hector Martin "marcan"
2017-06-20 19:07 ` Kees Cook
2017-06-20 20:22 ` Hector Martin "marcan"
2017-06-20 19:14 ` [kernel-hardening] " Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb9f92d2-6737-d9ae-ed49-fa61a089c727@linux.com \
--to=alex.popov@linux.com \
--cc=ard.biesheuvel@linaro.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=mark.rutland@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.