linux-kernel - Re: [PATCH 2/3] rust: miscdevice: Implemented `read` and `write`

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: <5cf242fd-ded4-4aea-a5b7-9c856f75fdb6@protonmail.com>
Date: Thu, 18 Sep 2025 15:57:15 +0000
From: ManeraKai <manerakai@...tonmail.com>
To: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Cc: "aliceryhl@...gle.com" <aliceryhl@...gle.com>, "arnd@...db.de" <arnd@...db.de>, "rust-for-linux@...r.kernel.org" <rust-for-linux@...r.kernel.org>, "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3] rust: miscdevice: Implemented `read` and `write`

 > What type of real misc driver do you want to write in rust that you
 > need a read/write callback and not just an ioctl one?

I don't have one in mind. I was reading your book and experimenting with 
char drivers. However, I found out that you prefer new developers to use 
misc instead:
https://lore.kernel.org/rust-for-linux/2024101256-amplifier-joylessly-6ca9@gregkh/

So, I wanted to safe-wrap misc for new Rust developers (me included). 
And go from there to write real drivers.