From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Sami Tolvanen <samitolvanen@google.com>,
Mark Rutland <mark.rutland@arm.com>,
James Morse <james.morse@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Kees Cook <keescook@chromium.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] scs: switch to vmapped shadow stacks
Date: Wed, 18 Nov 2020 09:27:37 +0000 [thread overview]
Message-ID: <20201118092736.GA1577@willie-the-truck> (raw)
In-Reply-To: <X7QJ3PbYm4kxGAEt@trantor>
On Tue, Nov 17, 2020 at 05:35:24PM +0000, Catalin Marinas wrote:
> On Thu, Oct 22, 2020 at 01:23:53PM -0700, Sami Tolvanen wrote:
> > As discussed a few months ago [1][2], virtually mapped shadow call stacks
> > are better for safety and robustness. This series dusts off the VMAP
> > option from the original SCS patch series and switches the kernel to use
> > virtually mapped shadow stacks unconditionally when SCS is enabled.
> >
> > [1] https://lore.kernel.org/lkml/20200515172355.GD23334@willie-the-truck/
> > [2] https://lore.kernel.org/lkml/20200427220942.GB80713@google.com/
> >
> >
> > Sami Tolvanen (2):
> > scs: switch to vmapped shadow stacks
> > arm64: scs: use vmapped IRQ and SDEI shadow stacks
>
> Will, Mark. Any objections to this series? If not, I can queue it for
> 5.11 via the arm64 tree.
It's on my list to review, but I have a tonne of other things I have to get
to first.
Will
prev parent reply other threads:[~2020-11-18 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 20:23 [PATCH 0/2] scs: switch to vmapped shadow stacks Sami Tolvanen
2020-10-22 20:23 ` [PATCH 1/2] " Sami Tolvanen
2020-10-22 22:38 ` Kees Cook
2020-11-19 13:00 ` Will Deacon
2020-11-20 17:00 ` Sami Tolvanen
2020-11-23 11:08 ` Will Deacon
2020-10-22 20:23 ` [PATCH 2/2] arm64: scs: use vmapped IRQ and SDEI " Sami Tolvanen
2020-10-22 22:38 ` Kees Cook
2020-11-19 13:11 ` Will Deacon
2020-11-17 17:35 ` [PATCH 0/2] scs: switch to vmapped " Catalin Marinas
2020-11-18 9:27 ` 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=20201118092736.GA1577@willie-the-truck \
--to=will@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=samitolvanen@google.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).