From: Sasha Levin <sashal@kernel.org>
To: David Long <dave.long@linaro.org>
Cc: stable@vger.kernel.org,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Florian Fainelli <f.fainelli@gmail.com>,
Julien Thierry <julien.thierry@arm.com>,
Tony Lindgren <tony@atomide.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Greg KH <gregkh@linuxfoundation.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 4.20 1/1] ARM: fix the cockup in the previous patch
Date: Sat, 26 Jan 2019 12:57:55 -0500 [thread overview]
Message-ID: <20190126175755.GA30183@sasha-vm> (raw)
In-Reply-To: <20190125224037.4787-2-dave.long@linaro.org>
On Fri, Jan 25, 2019 at 05:40:37PM -0500, David Long wrote:
>From: Russell King <rmk+kernel@armlinux.org.uk>
>
>Commit d6951f582cc50ba0ad22ef46b599740966599b14 upstream.
>
>The intention in the previous patch was to only place the processor
>tables in the .rodata section if big.Little was being built and we
>wanted the branch target hardening, but instead (due to the way it
>was tested) it ended up always placing the tables into the .rodata
>section.
>
>Although harmless, let's correct this anyway.
>
>Fixes: 3a4d0c2172bc ("ARM: ensure that processor vtables is not lost after boot")
>Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
>Signed-off-by: David A. Long <dave.long@linaro.org>
Queued for 4.20, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-01-26 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 22:40 [PATCH 4.20 0/1] Fix regression from arm spectre patch series David Long
2019-01-25 22:40 ` [PATCH 4.20 1/1] ARM: fix the cockup in the previous patch David Long
2019-01-26 17:57 ` Sasha Levin [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=20190126175755.GA30183@sasha-vm \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=dave.long@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=julien.thierry@arm.com \
--cc=linux@armlinux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=stable@vger.kernel.org \
--cc=tony@atomide.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