From: Greg KH <gregkh@linuxfoundation.org>
To: Lucas Wei <lucaswei@google.com>
Cc: stable@vger.kernel.org, robinpeng@google.com,
willdeacon@google.com, aaronding@google.com,
danielmentz@google.com, James Morse <james.morse@arm.com>
Subject: Re: [PATCH] arm64: errata: Add Cortex-A510 to the repeat tlbi list
Date: Tue, 30 Aug 2022 17:22:01 +0200 [thread overview]
Message-ID: <Yw4rGZ2LFgQN8qeB@kroah.com> (raw)
In-Reply-To: <20220830150804.3425929-1-lucaswei@google.com>
On Tue, Aug 30, 2022 at 11:08:04PM +0800, Lucas Wei wrote:
> From: James Morse <james.morse@arm.com>
>
> Cortex-A510 is affected by an erratum where in rare circumstances the
> CPUs may not handle a race between a break-before-make sequence on one
> CPU, and another CPU accessing the same page. This could allow a store
> to a page that has been unmapped.
>
> Work around this by adding the affected CPUs to the list that needs
> TLB sequences to be done twice.
>
> Signed-off-by: James Morse <james.morse@arm.com>
> Link: https://lore.kernel.org/r/20220704155732.21216-1-james.morse@arm.com
> Signed-off-by: Will Deacon <will@kernel.org>
> ---
> Documentation/arm64/silicon-errata.rst | 2 ++
> arch/arm64/Kconfig | 17 +++++++++++++++++
> arch/arm64/kernel/cpu_errata.c | 8 +++++++-
> 3 files changed, 26 insertions(+), 1 deletion(-)
What is the upstream commit id of this patch in Linus's tree, and what
tree(s) do you want it applied to?
Always be specific, remember, some of us have to deal with over a
thousand emails a day...
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-30 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 15:08 [PATCH] arm64: errata: Add Cortex-A510 to the repeat tlbi list Lucas Wei
2022-08-30 15:13 ` Lucas Wei
2022-08-30 15:22 ` Greg KH
2022-08-30 15:22 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-31 13:27 Lucas Wei
2022-09-01 9:56 ` Greg KH
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=Yw4rGZ2LFgQN8qeB@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aaronding@google.com \
--cc=danielmentz@google.com \
--cc=james.morse@arm.com \
--cc=lucaswei@google.com \
--cc=robinpeng@google.com \
--cc=stable@vger.kernel.org \
--cc=willdeacon@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