linux-kernel - Re: [PATCH v6 3/6] rust: irq: add support for non-threaded IRQs and handlers

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: <AACC99CD-086A-45AB-929C-7F25AABF8B6E@collabora.com>
Date: Sun, 13 Jul 2025 12:32:27 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Daniel Almeida <daniel.almeida@...labora.com>
Cc: Danilo Krummrich <dakr@...nel.org>,
 Benno Lossin <lossin@...nel.org>,
 Miguel Ojeda <ojeda@...nel.org>,
 Alex Gaynor <alex.gaynor@...il.com>,
 Boqun Feng <boqun.feng@...il.com>,
 Gary Guo <gary@...yguo.net>,
 Björn Roy Baron <bjorn3_gh@...tonmail.com>,
 Andreas Hindborg <a.hindborg@...nel.org>,
 Alice Ryhl <aliceryhl@...gle.com>,
 Trevor Gross <tmgross@...ch.edu>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 "Rafael J. Wysocki" <rafael@...nel.org>,
 Thomas Gleixner <tglx@...utronix.de>,
 Bjorn Helgaas <bhelgaas@...gle.com>,
 Krzysztof Wilczyński <kwilczynski@...nel.org>,
 linux-kernel@...r.kernel.org,
 rust-for-linux@...r.kernel.org,
 linux-pci@...r.kernel.org
Subject: Re: [PATCH v6 3/6] rust: irq: add support for non-threaded IRQs and
 handlers

> On 13 Jul 2025, at 12:28, Daniel Almeida <daniel.almeida@...labora.com> wrote:
> 
> 
> 
>> 
>> (2) Owning a reference count of a device (i.e. ARef<Device>) does *not*
>>     guarantee that the device is bound. You can own a reference count to the
>>     device object way beyond it being bound. Instead, the guarantee comes from
>>     the scope.
>> 
>>     In this case, the scope is the IRQ callback, since the irq::Registration
>>     guarantees to call and complete free_irq() before the underlying bus
>>     device is unbound.
>> 
> 
> 
> Oh, I see. I guess this is where I started to get a bit confused indeed.
> 
> — Daniel

Fine, I guess I can submit a newer version and test that on Tyr.

Dirk, can you also test the next iteration on your driver? It will possibly
solve your use case as well.

— Daniel