From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-rt-devel@lists.linux.dev,
Xie Yuanbin <xieyuanbin1@huawei.com>,
Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
"Yadi.hu" <yadi.hu@windriver.com>
Subject: Re: [PATCH v3 2/5] ARM: mm: fault: Enable interrupts before invoking __do_user_fault()
Date: Tue, 2 Dec 2025 15:46:25 +0000 [thread overview]
Message-ID: <aS8J0WrmmH01L3K1@shell.armlinux.org.uk> (raw)
In-Reply-To: <20251202141816.wfHNUMFK@linutronix.de>
On Tue, Dec 02, 2025 at 03:18:16PM +0100, Sebastian Andrzej Siewior wrote:
> On 2025-11-10 15:55:52 [+0100], To linux-arm-kernel@lists.infradead.org wrote:
> |
> | https://www.armlinux.org.uk/developer/patches/viewpatch.php?id=9460/1
> |
> | Moved to Discarded.
> |
> | This makes the issues with the branch predictor hardening worse if this
> | patch is merged on its own - since this adds another path where
> | interrupts are enabled before calling harden_branch_predictor() in
> | __do_user_fault(). It would be sensible to move the interrupt enable
> | into __do_user_fault().
> |
> | *** PLEASE DO NOT REPLY TO THIS MESSAGE ***
>
> I thought that we apply both.
> In 9462/1 I am moving harden_branch_predictor() out of __do_user_fault()
> because do_page_fault() needs the hardening before the interrupts are
> enabled. Do mean something like
If I apply 9460/1 without 9462/1 first, then it makes the problems
with the branch predictor hardening worse. I'm not prepared to do that.
However, 9462/1 is tied up in the discussions that are ongoing, and I'm
not going to short-circuit the still-ongoing discussions that touch
this area by applying this patch - which would screw up everyone's
proposals to fix the various many problems that are being discovered in
the 32-bit ARM fault handling.
This means I can't apply 9462/1 nor 9460/1.
Since 9463/1 likely requires these, I can't apply that one either.
Sorry.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-12-02 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 14:55 [PATCH v3 0/5] ARM: Remaining PREEMPT_RT bits Sebastian Andrzej Siewior
2025-11-10 14:55 ` [PATCH v3 1/5] ARM: mm: fault: Move harden_branch_predictor() before interrupts are enabled Sebastian Andrzej Siewior
2025-11-10 14:55 ` [PATCH v3 2/5] ARM: mm: fault: Enable interrupts before invoking __do_user_fault() Sebastian Andrzej Siewior
2025-12-02 14:18 ` Sebastian Andrzej Siewior
2025-12-02 15:46 ` Russell King (Oracle) [this message]
2025-12-02 16:05 ` Sebastian Andrzej Siewior
2025-11-10 14:55 ` [PATCH v3 3/5] ARM: Disable jump-label on PREEMPT_RT Sebastian Andrzej Siewior
2025-11-10 14:55 ` [PATCH v3 4/5] ARM: Disable HIGHPTE on PREEMPT_RT kernels Sebastian Andrzej Siewior
2025-11-10 14:55 ` [PATCH v3 5/5] ARM: Allow to enable RT Sebastian Andrzej Siewior
2025-11-11 15:16 ` [PATCH v3 0/5] ARM: Remaining PREEMPT_RT bits Arnd Bergmann
2025-11-11 15:59 ` Sebastian Andrzej Siewior
2025-11-12 2:53 ` Bryan Brattlof
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=aS8J0WrmmH01L3K1@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=xieyuanbin1@huawei.com \
--cc=yadi.hu@windriver.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;
as well as URLs for NNTP newsgroup(s).