From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, Ard Biesheuvel <ardb@kernel.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
alexandru.elisei@arm.com
Subject: Re: [PATCH] arm64/alternatives: don't patch up internal branches
Date: Thu, 9 Jul 2020 16:49:42 +0100 [thread overview]
Message-ID: <159430308159.1640844.14611148897545561073.b4-ty@kernel.org> (raw)
In-Reply-To: <20200709125953.30918-1-ardb@kernel.org>
On Thu, 9 Jul 2020 15:59:53 +0300, Ard Biesheuvel wrote:
> Commit f7b93d429 ("arm64/alternatives: use subsections for replacement
> sequences") moved the alternatives replacement sequences into subsections,
> in order to keep the as close as possible to the code that they replace.
>
> Unfortunately, this broke the logic in branch_insn_requires_update,
> which assumed that any branch into kernel executable code was a branch
> that required updating, which is no longer the case now that the code
> sequences that are patched in are in the same section as the patch site
> itself.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/alternatives: don't patch up internal branches
https://git.kernel.org/arm64/c/5679b2814219
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-07-09 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 12:59 [PATCH] arm64/alternatives: don't patch up internal branches Ard Biesheuvel
2020-07-09 13:14 ` Alexandru Elisei
2020-07-09 15:49 ` 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=159430308159.1640844.14611148897545561073.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.