linux-kernel - Re: [PATCH] genirq/manage: Reduce priority of forced secondary IRQ handler

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: <1b3684b424af051b5cb1fbce9ab65fc5cdf2b1a1.camel@redhat.com>
Date: Fri, 03 Oct 2025 13:25:53 -0500
From: Crystal Wood <crwood@...hat.com>
To: Lukas Wunner <lukas@...ner.de>, Thomas Gleixner <tglx@...utronix.de>
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>, Ingo Molnar	
 <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>, Juri Lelli	
 <juri.lelli@...hat.com>, Vincent Guittot <vincent.guittot@...aro.org>,
 Clark Williams <clrkwllms@...nel.org>, Steven Rostedt
 <rostedt@...dmis.org>, Dietmar Eggemann	 <dietmar.eggemann@....com>, Ben
 Segall <bsegall@...gle.com>, Mel Gorman	 <mgorman@...e.de>, Valentin
 Schneider <vschneid@...hat.com>, 	linux-kernel@...r.kernel.org, Attila
 Fazekas <afazekas@...hat.com>, 	linux-pci@...r.kernel.org,
 linux-rt-devel@...ts.linux.dev, Bjorn Helgaas	 <helgaas@...nel.org>, Mahesh
 J Salgaonkar <mahesh@...ux.ibm.com>, Oliver OHalloran <oohall@...il.com>
Subject: Re: [PATCH] genirq/manage: Reduce priority of forced secondary IRQ
 handler

On Sun, 2025-09-21 at 15:12 +0200, Lukas Wunner wrote:
> On Sat, Sep 20, 2025 at 11:20:26PM +0200, Thomas Gleixner wrote:
> > I obviously understand that the proposed change squashs the whole class
> > of similar (not yet detected) issues, but that made me look at that
> > particular instance nevertheless.
> > 
> > All aer_irq() does is reading two PCI config words, writing one and then
> > sticking 64bytes into a KFIFO. All of that is hard interrupt safe. So
> > arguably this AER problem can be nicely solved by the below one-liner,
> > no?
> 
> The one-liner (which sets IRQF_NO_THREAD) was what Crystal originally
> proposed:
> 
> https://lore.kernel.org/r/20250902224441.368483-1-crwood@redhat.com/

So, is the plan to apply the original patch then?


Thanks,
Crystal