linux-kernel - Re: [patch V3 20/20] sched/mmcid: Switch over to the new mechanism

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: <lhuy0nvlios.fsf@oldenburg.str.redhat.com>
Date: Mon, 24 Nov 2025 13:27:15 +0100
From: Florian Weimer <fweimer@...hat.com>
To: Mark Brown <broonie@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,  LKML
 <linux-kernel@...r.kernel.org>,  Peter Zijlstra <peterz@...radead.org>,
  Gabriele Monaco <gmonaco@...hat.com>,  Mathieu Desnoyers
 <mathieu.desnoyers@...icios.com>,  Michael Jeanson
 <mjeanson@...icios.com>,  Jens Axboe <axboe@...nel.dk>,  "Paul E.
 McKenney" <paulmck@...nel.org>,  "Gautham R. Shenoy"
 <gautham.shenoy@....com>,  Tim Chen <tim.c.chen@...el.com>,  Yury Norov
 <yury.norov@...il.com>,  Shrikanth Hegde <sshegde@...ux.ibm.com>
Subject: Re: [patch V3 20/20] sched/mmcid: Switch over to the new mechanism

* Mark Brown:

> On Wed, Oct 29, 2025 at 02:09:32PM +0100, Thomas Gleixner wrote:
>> Now that all pieces are in place, change the implementations of
>> sched_mm_cid_fork() and sched_mm_cid_exit() to adhere to the new strict
>> ownership scheme and switch context_switch() over to use the new
>> mm_cid_schedin() functionality.
>> 
>> The common case is that there is no mode change required, which makes
>> fork() and exit() just update the user count and the constraints.
>
> I'm seeing boot failures on x86 qemu in -next which bisect to this
> patch.  The boot gets to userspace but then grinds to a halt:
>
>     https://lava.sirena.org.uk/scheduler/job/2118455#L542
>
> which isn't terribly informative unfortunately.  I don't have any x86
> hardware, and nothing else seems affected.

I believe that's already discussed here:

  <https://lore.kernel.org/873466jekm.ffs@tglx/>

Thanks,
Florian