linux-kernel - Re: [PATCH] irqchip/gic-v3-its: Don't acquire rt_spin_lock in allocate_vpe_l1

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] [day] [month] [year] [list]

Message-ID: <70dbf293-dd5b-4d77-b653-8f8c09129723@redhat.com>
Date: Wed, 21 Jan 2026 22:49:35 -0500
From: Waiman Long <llong@...hat.com>
To: Marc Zyngier <maz@...nel.org>, Thomas Gleixner <tglx@...nel.org>
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
 Clark Williams <clrkwllms@...nel.org>, Steven Rostedt <rostedt@...dmis.org>,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 linux-rt-devel@...ts.linux.dev
Subject: Re: [PATCH] irqchip/gic-v3-its: Don't acquire rt_spin_lock in
 allocate_vpe_l1_table()


On 1/21/26 3:41 PM, Waiman Long wrote:
>
>>> Waiman, can you please give the following hack a go on your box? The
>>> machines I have are thankfully limited to a single ITS group, so I
>>> can't directly reproduce your issue.
>> Have you managed to try this hack? I may be able to spend some time
>> addressing the issue in the next cycle if I have an indication that
>> I'm on the right track.
>
> Yes, I have tried out your hack patch and the 2-socket Grace test 
> system booted up without producing any bug report for a RT debug 
> kernel. I will try out your official patch once it come out. So moving 
> the memory allocation to a later part of the hotplug bringup pipeline 
> where sleeping is allowed should work. 

Attaching the dmesg log for your further investigation.

Cheers,
Longman

View attachment "dmesg.log" of type "text/x-log" (198417 bytes)