From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: stable@vger.kernel.org
Cc: Bryan Brattlof <bb@ti.com>,
Daniel Wagner <daniel.wagner@monom.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
cip-dev@lists.cip-project.org,
nobuhiro.iwamatsu.x90@mail.toshiba, pavel@nabladev.com,
Russell King <rmk+kernel@armlinux.org.uk>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [PATCH 0/4] ARM: v6.6 and v6.1 stable backports
Date: Mon, 22 Jun 2026 12:26:30 +0200 [thread overview]
Message-ID: <20260622102634.780100-1-bigeasy@linutronix.de> (raw)
This is a backport of ARM related fixes. This applies cleanly to v6.6
and v6.1. The v6.18 and v6.12 trees already contain this.
I've been looking at v5.15 and it seems there is code missing so I am
not enitrely sure if it makes sense to backport the last two patches of
the series any further than v6.1. Therefore I am stopping here ;)
#1 and #2 are prerequisites for #3.
Russell King (Oracle) (4):
ARM: group is_permission_fault() with is_translation_fault()
ARM: allow __do_kernel_fault() to report execution of memory faults
ARM: fix hash_name() fault
ARM: fix branch predictor hardening
arch/arm/mm/alignment.c | 4 ++
arch/arm/mm/fault.c | 94 +++++++++++++++++++++++++++++++----------
2 files changed, 76 insertions(+), 22 deletions(-)
--
2.53.0
next reply other threads:[~2026-06-22 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 10:26 Sebastian Andrzej Siewior [this message]
2026-06-22 10:26 ` [PATCH 1/4] ARM: group is_permission_fault() with is_translation_fault() Sebastian Andrzej Siewior
2026-06-22 10:26 ` [PATCH 2/4] ARM: allow __do_kernel_fault() to report execution of memory faults Sebastian Andrzej Siewior
2026-06-22 10:26 ` [PATCH 3/4] ARM: fix hash_name() fault Sebastian Andrzej Siewior
2026-06-22 10:26 ` [PATCH 4/4] ARM: fix branch predictor hardening Sebastian Andrzej Siewior
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=20260622102634.780100-1-bigeasy@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=bb@ti.com \
--cc=cip-dev@lists.cip-project.org \
--cc=daniel.wagner@monom.org \
--cc=jan.kiszka@siemens.com \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@nabladev.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stable@vger.kernel.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