linux-kernel - Re: REGRESSION on linux-next (next-20260115)

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: <20260121075348.5MyqcHFB@linutronix.de>
Date: Wed, 21 Jan 2026 08:53:48 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@...el.com>
Cc: hansg@...nel.org, "Kurmi, Suresh Kumar" <suresh.kumar.kurmi@...el.com>,
	"Saarinen, Jani" <jani.saarinen@...el.com>,
	"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
	"intel-xe@...ts.freedesktop.org" <intel-xe@...ts.freedesktop.org>,
	linux-kernel@...r.kernel.org, linux-rt-devel@...ts.linux.dev,
	sfr@...b.auug.org.au, ilpo.jarvinen@...ux.intel.com,
	regressions@...mhuis.info
Subject: Re: REGRESSION on linux-next (next-20260115)

On 2026-01-21 12:42:16 [+0530], Borah, Chaitanya Kumar wrote:
> commit aef30c8d569c0f31715447525640044c74feb26f
> Author: Sebastian Andrzej Siewior bigeasy@...utronix.de
> Date:   Mon Jan 12 14:40:13 2026 +0100
> 
> 
>     genirq: Warn about using IRQF_ONESHOT without a threaded handler
> `````````````````````````````````````````````````````````````````````````````````````````````````````````
> 
> Looking at the irq register code in int0002_vgpio.c, it seems the warning
> comes from
> 
>         ret = devm_request_irq(dev, irq, int0002_irq,
>                                IRQF_ONESHOT | IRQF_SHARED, "INT0002", chip);
> 
> Looking at the history, this flag was added by the Commit 8f812373d195
> ("platform/x86: intel: int0002_vgpio: Pass IRQF_ONESHOT to request_irq()")
> to resolve another issue.
> 
> Any proposals for solving the WARN_ON?

Do you have the ACPI interrupt also on the same interrupt on the board
in question?

Sebastian