linux-kernel - Re: [PATCH 1/2] linux/interrupt.h: allow "guard" notation to disable and reenable IRQ with valid IRQ check

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: <66ff3c90-8c14-462d-9a86-0a3ff1df2c25@mailbox.org>
Date: Thu, 22 Jan 2026 20:11:02 +0100
From: Marek Vasut <marek.vasut@...lbox.org>
To: Frank Li <Frank.li@....com>, Marek Vasut <marek.vasut+renesas@...lbox.org>
Cc: linux-input@...r.kernel.org, "Peter Zijlstra (Intel)"
 <peterz@...radead.org>, Cheng-Yang Chou <yphbchou0911@...il.com>,
 Dmitry Torokhov <dmitry.torokhov@...il.com>,
 Geert Uytterhoeven <geert+renesas@...der.be>,
 Jinjie Ruan <ruanjinjie@...wei.com>,
 Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>,
 Marc Zyngier <maz@...nel.org>,
 Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
 Thomas Gleixner <tglx@...nel.org>, linux-kernel@...r.kernel.org,
 linux-renesas-soc@...r.kernel.org
Subject: Re: [PATCH 1/2] linux/interrupt.h: allow "guard" notation to disable
 and reenable IRQ with valid IRQ check

On 1/22/26 4:38 PM, Frank Li wrote:
> On Thu, Jan 22, 2026 at 12:23:47AM +0100, Marek Vasut wrote:
>> Introduce disable_valid_irq scoped guard. This is an extension
>> of disable_irq scoped guard, which disables and enables IRQs
>> around a scope. The disable_valid_irq scoped guard does almost
>> the same, except it handles the case where IRQ is not valid,
>> in which case it does not do anything. This is meant to be used
>> by for example touch controller drivers, which can do both IRQ
>> driven and polling mode of operation, and this makes their code
>> slighly simpler.
> 
> I think it'd better to give simple example here.
Patch 2/2 is that example , but I can also include it in the commit 
message if this 1/2 is even acceptable.