From: Niels Pressel <npressel@ethz.ch>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: tip-bot2 for Niels Pressel <tip-bot2@linutronix.de>,
linux-tip-commits@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [tip: core/urgent] entry/rseq: Fix hard lockup on granted time slice extension
Date: Sun, 9 Aug 2026 09:29:46 +0200 [thread overview]
Message-ID: <angoA9-54RR-rUB4@ethz.ch> (raw)
In-Reply-To: <87y0ehmy3c.ffs@fw13>
On Fri, Aug 07, 2026 at 11:15:19PM +0100, Thomas Gleixner wrote:
> That's user access which requires interrupts to be enabled.
Ah yes, I missed that the rseq memory might be paged out.
> Niels' original patch was correct.
Okay, I'll revert to the v1 approach for v3.
prev parent reply other threads:[~2026-08-09 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 11:34 [PATCH v2] rseq: fix hard lockup on granted time slice extension Niels Pressel
2026-08-06 12:48 ` [tip: core/urgent] entry/rseq: Fix " tip-bot2 for Niels Pressel
2026-08-07 21:15 ` Thomas Gleixner
2026-08-08 8:36 ` Peter Zijlstra
2026-08-08 11:23 ` Thomas Gleixner
2026-08-09 7:29 ` Niels Pressel [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=angoA9-54RR-rUB4@ethz.ch \
--to=npressel@ethz.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tip-bot2@linutronix.de \
--cc=x86@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