linux-kernel - Re: [PATCH v16 7/7] timers/migration: Exclude isolated cpus from hierarchy

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: <0c5d224858b31f66a9a166c990a393cb2a121162.camel@redhat.com>
Date: Thu, 20 Nov 2025 16:23:18 +0100
From: Gabriele Monaco <gmonaco@...hat.com>
To: Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org, 
 Anna-Maria Behnsen <anna-maria@...utronix.de>, Frederic Weisbecker
 <frederic@...nel.org>, Waiman Long <longman@...hat.com>
Cc: "John B. Wyatt IV" <jwyatt@...hat.com>, "John B. Wyatt IV"
	 <sageofredondo@...il.com>
Subject: Re: [PATCH v16 7/7] timers/migration: Exclude isolated cpus from
 hierarchy

On Thu, 2025-11-20 at 16:21 +0100, Thomas Gleixner wrote:
> On Thu, Nov 20 2025 at 15:56, Gabriele Monaco wrote:
> > + * This function returns false during early boot and the isolation logic is
> > + * enabled only after isolated CPUs are marked as unavailable at late boot.
> > + * The tick CPU can be isolated at boot, however we cannot mark it as
> > + * unavailable to avoid having no global migrator for the nohz_full CPUs.
> > This
> > + * should be ensured by the callers of this function: implicitly from
> > hotplug
> > + * callbacs and explicitly in tmigr_init_isolation() and
> 
> 'callbacs' is still not correct :)
> 
> Other than that:
> 
> Reviewed-by: Thomas Gleixner <tglx@...utronix.de>

Damn, I knew I was missing something..
Should I send a v17 for this or just re-send this patch?

Thanks,
Gabriele