linux-kernel - [PATCH 0/3] firewire: ohci: switch to threaded IRQ handler for SelfIDComplete event

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

Message-ID: <20250823030954.268412-1-o-takashi@sakamocchi.jp>
Date: Sat, 23 Aug 2025 12:09:51 +0900
From: Takashi Sakamoto <o-takashi@...amocchi.jp>
To: linux1394-devel@...ts.sourceforge.net
Cc: linux-kernel@...r.kernel.org
Subject: [PATCH 0/3] firewire: ohci: switch to threaded IRQ handler for SelfIDComplete event

Hi,

This patchset replaces the module-local workqueue with a threaded IRQ
handler for handling the SelfIDComplete event in the 1394 OHCI PCI driver.

The SelfIDComplete event is the first step in maintaining bus topology.
It occurs after a bus reset or when the topology changes, and must be
processed outside the hard IRQ context due to the latency involved in
enumerating the SelfID sequence. Historically, this was handled by a
module-local workqueue with the WQ_MEM_RECLAIM flag. A threaded IRQ
handler offers a cleaner and more reliable solution, leveraging the
kernel's common infrastructure and eliminating the need for maintaining
a custom workqueue.

Takashi Sakamoto (3):
  firewire: ohci: move self_id_complete tracepoint after validating
    register
  firewire: ohci: use threaded IRQ handler to handle SelfIDComplete
    event
  firewire: ohci: remove module-local workqueue

 drivers/firewire/ohci.c | 61 +++++++++++++++++------------------------
 1 file changed, 25 insertions(+), 36 deletions(-)

base-commit: 8748368c3d92f7bdef67c90d3f62ab92083b3677
-- 
2.48.1