From: Xie Yuanbin <xieyuanbin1@huawei.com>
To: <sashal@kernel.org>, <gregkh@linuxfoundation.org>,
<linux@armlinux.org.uk>, <bigeasy@linutronix.de>,
<clrkwllms@kernel.org>, <rostedt@goodmis.org>,
<rmk+kernel@armlinux.org.uk>, <linusw@kernel.org>,
<kuninori.morimoto.gx@renesas.com>, <arnd@arndb.de>,
<xiqi2@huawei.com>, <ljs@kernel.org>, <wozizhi@huaweicloud.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-rt-devel@lists.linux.dev>,
<stable@vger.kernel.org>, <patches@lists.linux.dev>,
<lisongze2@huawei.com>, <wangbing6@huawei.com>,
Xie Yuanbin <xieyuanbin1@huawei.com>
Subject: [PATCH 5.10.y/5.15.y 0/4] ARM: fix might_sleep() WARNING for mmap_write_lock() around show_pte()
Date: Wed, 16 Sep 2026 16:48:07 +0800 [thread overview]
Message-ID: <20260916084807.176359-1-xieyuanbin1@huawei.com> (raw)
In-Reply-To: <20260916080011.170295-1-xieyuanbin1@huawei.com>
On linux-5.10.y and linux-5.15.y, commit 07e4d5380f2a844ab7a1 ("ARM:
9485/1: mm: acquire mmap write lock around show_pte() for user faults")
introduces a might_sleep() WARNING when using mmap write lock. This is
due to the lack of upstream commit 59e4f3b45b96a24fc9b7 ("ARM: ensure
interrupts are enabled in __do_user_fault()") and
commit e79ca91165d4fd18549c ("ARM: 9484/1: enable interrupts when
unhandled user faults are triggered") .
This series backports all these upstream patches into the linux-5.10.y:
1. commit 7733bc7d299d682f2723 ("ARM: fix hash_name() fault")
2. commit fd2dee1c6e2256f726ba ("ARM: fix branch predictor hardening")
3. commit 59e4f3b45b96a24fc9b7 ("ARM: ensure interrupts are enabled in
__do_user_fault()")
4. commit e79ca91165d4fd18549c ("ARM: 9484/1: enable interrupts when
unhandled user faults are triggered")
In the upstream version, the following patches are a patch set:
a. commit dea20281ac8822661576 ("ARM: group is_permission_fault() with
is_translation_fault()")
b. commit 40b466db1dffb41f0529 ("ARM: allow __do_kernel_fault() to report
execution of memory faults")
c. commit 7733bc7d299d682f2723 ("ARM: fix hash_name() fault"):
which is 1.
d. commit fd2dee1c6e2256f726ba ("ARM: fix branch predictor hardening"):
which is 2.
The fixed issues by this patch set also exist in linux-5.10 && linux-5.15.
a. and b. do not need to be backported, and after c. and d.
is backported, 3. and 4. can be safely patched.
next prev parent reply other threads:[~2026-09-16 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 8:00 [PATCH 5.10.y/5.15.y 1/4] ARM: fix hash_name() fault Xie Yuanbin
2026-09-16 8:00 ` [PATCH 5.10.y/5.15.y 2/4] ARM: fix branch predictor hardening Xie Yuanbin
2026-09-16 8:00 ` [PATCH 5.10.y/5.15.y 3/4] ARM: ensure interrupts are enabled in __do_user_fault() Xie Yuanbin
2026-09-16 8:00 ` [PATCH 5.10.y/5.15.y 4/4] ARM: 9484/1: enable interrupts when unhandled user faults are triggered Xie Yuanbin
2026-09-16 19:28 ` Sasha Levin
2026-09-16 8:48 ` Xie Yuanbin [this message]
2026-09-16 19:27 ` [PATCH 5.10.y/5.15.y 1/4] ARM: fix hash_name() fault Sasha Levin
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=20260916084807.176359-1-xieyuanbin1@huawei.com \
--to=xieyuanbin1@huawei.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux@armlinux.org.uk \
--cc=lisongze2@huawei.com \
--cc=ljs@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wangbing6@huawei.com \
--cc=wozizhi@huaweicloud.com \
--cc=xiqi2@huawei.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