From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc4
Date: Fri, 3 Dec 2021 13:19:38 +0000 [thread overview]
Message-ID: <20211203131937.GA27943@willie-the-truck> (raw)
Hi Linus,
Please pull these three arm64 fixes for -rc4. One of them is just a
trivial documentation fix, whereas the other two address a warning in
the kexec code and a crash in ftrace on systems implementing BTI. The
latter patch has a couple of ugly ifdefs which Mark plans to clean up
separately, but as-is the patch is straightforward for backporting to
stable kernels.
Cheers,
Will
--->8
The following changes since commit 94902d849e85093aafcdbea2be8e2beff47233e6:
arm64: uaccess: avoid blocking within critical sections (2021-11-24 09:16:26 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
for you to fetch changes up to 35b6b28e69985eafb20b3b2c7bd6eca452b56b53:
arm64: ftrace: add missing BTIs (2021-12-02 10:18:32 +0000)
----------------------------------------------------------------
arm64 fixes for -rc4
- Add missing BTI landing instructions to the ftrace*_caller trampolines
- Fix kexec() WARN when DEBUG_VIRTUAL is enabled
- Fix PAC documentation by removing stale references to compiler flags
----------------------------------------------------------------
Kuan-Ying Lee (1):
arm64: update PAC description for kernel
Mark Rutland (2):
arm64: kexec: use __pa_symbol(empty_zero_page)
arm64: ftrace: add missing BTIs
Documentation/arm64/pointer-authentication.rst | 9 ++++-----
arch/arm64/kernel/entry-ftrace.S | 6 ++++++
arch/arm64/kernel/machine_kexec.c | 2 +-
3 files changed, 11 insertions(+), 6 deletions(-)
next reply other threads:[~2021-12-03 13:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 13:19 Will Deacon [this message]
2021-12-03 18:53 ` [GIT PULL] arm64 fixes for -rc4 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 10:29 Will Deacon
2023-01-13 13:58 ` pr-tracker-bot
2022-09-02 11:12 Will Deacon
2022-09-02 18:30 ` pr-tracker-bot
2022-04-22 11:20 Will Deacon
2022-04-22 21:19 ` pr-tracker-bot
2020-11-13 12:39 GIT " Will Deacon
2020-11-13 12:44 ` [GIT " Will Deacon
2020-11-13 17:25 ` Linus Torvalds
2020-07-04 13:05 Will Deacon
2020-07-05 17:35 ` pr-tracker-bot
2019-10-17 23:43 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-18 0:06 ` Linus Torvalds
2019-10-18 17:41 ` Will Deacon
2019-10-18 19:17 ` Linus Torvalds
2019-10-21 6:46 ` Ingo Molnar
2019-10-21 11:45 ` Linus Torvalds
2019-10-22 8:16 ` Uwe Kleine-König
2019-10-18 0:15 ` pr-tracker-bot
2019-10-18 20:09 ` Jayachandran Chandrasekharan Nair
2019-06-07 15:13 [GIT PULL] arm64: fixes " Will Deacon
2019-06-07 16:45 ` pr-tracker-bot
2019-04-05 17:17 [GIT PULL] arm64 " Catalin Marinas
2019-04-05 23:50 ` pr-tracker-bot
2018-09-14 16:19 [GIT PULL] arm64: " Will Deacon
2017-12-15 18:31 Will Deacon
2017-08-04 18:32 Will Deacon
2016-06-17 17:07 Will Deacon
2015-05-14 15:48 Will Deacon
2015-01-09 15:22 Will Deacon
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=20211203131937.GA27943@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=torvalds@linux-foundation.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 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).