linux-kernel - Re: [PATCH 2/3] device: rust: expand documentation for Device

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: <DBHQ2ZDUHLSW.LHWUTFQO1E60@kernel.org>
Date: Mon, 21 Jul 2025 14:13:14 +0200
From: "Danilo Krummrich" <dakr@...nel.org>
To: "Alice Ryhl" <aliceryhl@...gle.com>
Cc: "Greg KH" <gregkh@...uxfoundation.org>, <rafael@...nel.org>,
 <ojeda@...nel.org>, <alex.gaynor@...il.com>, <boqun.feng@...il.com>,
 <gary@...yguo.net>, <bjorn3_gh@...tonmail.com>, <lossin@...nel.org>,
 <a.hindborg@...nel.org>, <tmgross@...ch.edu>,
 <rust-for-linux@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3] device: rust: expand documentation for Device

On Mon Jul 21, 2025 at 2:07 PM CEST, Alice Ryhl wrote:
> The connection is that to request an irq you must have a &Device<Bound>,
> so if you can only obtain a &Device<Bound> to a bus device, then that
> means that you can never request an irq for a class device.

As mentioned in my other reply, a class device never owns resources of a "real"
device such as an IRQ.

A USB device, which represents a real device on a bus, is a bus device, in your
example the class device is the input device.