From: Will Deacon <will.deacon@arm.com>
To: Kees Cook <keescook@chromium.org>
Cc: Laura Abbott <labbott@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Alexander Popov <alex.popov@linux.com>
Subject: Re: [PATCH] arm64: Clear the stack
Date: Thu, 12 Jul 2018 13:10:40 +0100 [thread overview]
Message-ID: <20180712121040.GB16043@arm.com> (raw)
In-Reply-To: <CAGXu5jLwhdKy6rfSKOeN2hajP5aCnYeT3yMka5ZbJ_o02z=WTA@mail.gmail.com>
On Wed, Jul 11, 2018 at 05:05:32PM -0700, Kees Cook wrote:
> On Fri, Jun 29, 2018 at 12:05 PM, Laura Abbott <labbott@redhat.com> wrote:
> > include/linux/stackleak.h | 1 +
> > [...]
> > diff --git a/include/linux/stackleak.h b/include/linux/stackleak.h
> > index e2da99b3a191..00d62b302efb 100644
> > --- a/include/linux/stackleak.h
> > +++ b/include/linux/stackleak.h
> > @@ -5,6 +5,7 @@
> > #include <linux/sched.h>
> > #include <linux/sched/task_stack.h>
> >
> > +#include <asm/stacktrace.h>
> > /*
> > * Check that the poison value points to the unused hole in the
> > * virtual memory map for your platform.
>
> FYI, I squashed this change into my copy of the stackleak v14 series.
> (And I just sent this arm64 patch with the adjustments for it to be
> stand-alone.)
I can't find that -- can you point me to it, please?
Will
prev parent reply other threads:[~2018-07-12 12:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 19:05 [PATCH] arm64: Clear the stack Laura Abbott
2018-06-29 19:47 ` Kees Cook
2018-06-29 20:19 ` Kees Cook
2018-06-29 20:22 ` Laura Abbott
2018-06-29 20:25 ` Kees Cook
2018-07-02 9:59 ` Will Deacon
2018-07-02 17:29 ` Kees Cook
2018-07-04 14:04 ` Will Deacon
2018-07-02 13:02 ` Alexander Popov
2018-07-02 18:48 ` Laura Abbott
2018-07-03 12:14 ` Mark Rutland
2018-07-03 15:03 ` Catalin Marinas
2018-07-03 20:38 ` Alexander Popov
2018-07-17 22:58 ` Laura Abbott
2018-07-19 10:41 ` Mark Rutland
2018-07-12 0:05 ` Kees Cook
2018-07-12 12:10 ` Will Deacon [this message]
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=20180712121040.GB16043@arm.com \
--to=will.deacon@arm.com \
--cc=alex.popov@linux.com \
--cc=ard.biesheuvel@linaro.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).