From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Sasha Levin <sashal@kernel.org>,
gregkh@linuxfoundation.org, szabolcs.nagy@arm.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] arm64: Always force a branch protection mode when the" failed to apply to 5.6-stable tree
Date: Thu, 16 Apr 2020 11:02:55 +0100 [thread overview]
Message-ID: <20200416100255.GC5354@sirena.org.uk> (raw)
In-Reply-To: <20200416093517.GA5354@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
On Thu, Apr 16, 2020 at 10:35:17AM +0100, Mark Brown wrote:
> On Thu, Apr 16, 2020 at 09:32:05AM +0100, Catalin Marinas wrote:
> > On Wed, Apr 15, 2020 at 09:51:21PM -0400, Sasha Levin wrote:
> > > I don't think that this is needed anywhere without 74afda4016a7 ("arm64:
> > > compile the kernel with ptrauth return address signing")?
> > Good point. Mark, is the Fixes line above correct or it should have been
> > the one Sasha mentions?
> Yes, Sasha's is right.
Actually, no - we do need a version of the fix for older versions prior
to the kernel having pointer auth support since the goal was to ensure
that the kernel doesn't actually get built with pointer auth when we are
doing it for userspace as that leaves us with half baked pointer auth in
the code. The original fixes was right and we want a redone backport.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-04-16 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 11:23 FAILED: patch "[PATCH] arm64: Always force a branch protection mode when the" failed to apply to 5.6-stable tree gregkh
2020-04-16 1:51 ` Sasha Levin
2020-04-16 8:32 ` Catalin Marinas
2020-04-16 9:35 ` Mark Brown
2020-04-16 10:02 ` Mark Brown [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=20200416100255.GC5354@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=szabolcs.nagy@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.