linux-kernel - [PATCH v3] sched/rt: Skip currently executing CPU in rto_next_cpu()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251204073544.458726-1-chenjinghuang2@huawei.com>
Date: Thu, 4 Dec 2025 07:35:44 +0000
From: Chen Jinghuang <chenjinghuang2@...wei.com>
To: <rostedt@...dmis.org>
CC: <bsegall@...gle.com>, <chenjinghuang2@...wei.com>,
	<dietmar.eggemann@....com>, <juri.lelli@...hat.com>,
	<linux-kernel@...r.kernel.org>, <mgorman@...e.de>, <mingo@...hat.com>,
	<peterz@...radead.org>, <vincent.guittot@...aro.org>, <vschneid@...hat.com>
Subject: [PATCH v3] sched/rt: Skip currently executing CPU in rto_next_cpu() - Request for merge

Hi Steven Rostedt,

This is a follow-up on my v3 patch for sched/rt: "Skip currently executing
CPU in rto_next_cpu()" (archive link:
https://lore.kernel.org/lkml/20251126055403.2076735-1-chenjinghuang2@huawei.com/)

You previously confirmed that this patch resolves the issue of a CPU
sending an IPI to itself. This patch has also fully resolved the issue
I encountered in my testing environment. Could you please help merge this
v3 patch into mainline? I'm happy to address any code review.

Thanks a lot for your time and review!