linux-kernel - Re: [PATCH v2] genirq: move clear of kstat_irqs to free

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: <87v7h5eu5m.ffs@tglx>
Date: Tue, 13 Jan 2026 10:31:01 +0100
From: Thomas Gleixner <tglx@...nel.org>
To: Luigi Rizzo <lrizzo@...gle.com>
Cc: Eric Dumazet <edumazet@...gle.com>, Marc Zyngier <maz@...nel.org>, Luigi
 Rizzo <rizzo.unipi@...il.com>, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] genirq: move clear of kstat_irqs to free_desc()

On Tue, Jan 13 2026 at 10:21, Luigi Rizzo wrote:
> On Tue, Jan 13, 2026, 10:09 Thomas Gleixner <tglx@...nel.org> wrote:
>> Right, though it really does not matter unless you deeply care about:
>>
>> alpha, arc, hexagon, m68k, mips, parisc, sparc, xtensa and random old
>> ARM32 platforms :)
>>
>
> Purely academic question: I suppose the lock is just to make sure that
> there isn't anyone currently using the descriptor before marking it
> disabled; but is it really needed, or by the time the function is called it
> is already known that it is not in use anymore?

It's still accessible through the array and while it's probably
irrelevant, I have no intention to audit all the legazy architecture
code for random abuse. At least the removed itanium code did nasty
things with them behind the core.

Thanks,

        tglx