On Thu, Sep 26, 2024 at 5:05 PM Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > On Thu, Sep 26, 2024 at 02:58:54PM +0000, Alice Ryhl wrote: > > A misc device is generally the best place to start with your first Rust > > driver, so having abstractions for miscdevice in Rust will be important > > for our ability to teach Rust to kernel developers. > > > > I intend to add a sample driver using these abstractions, and I also > > intend to use it in Rust Binder to handle the case where binderfs is > > turned off. > > > > I know that the patchset is still a bit rough. It could use some work on > > the file position aspect. But I'm sending this out now to get feedback > > on the overall approach. > > Very cool! > > > This patchset depends on files [1] and vma [2]. > > > > Link: https://lore.kernel.org/all/20240915-alice-file-v10-0-88484f7a3dcf@xxxxxxxxxx/ [1] > > Link: https://lore.kernel.org/all/20240806-vma-v5-1-04018f05de2b@xxxxxxxxxx/ [2] > > Signed-off-by: Alice Ryhl <aliceryhl@xxxxxxxxxx> > > Does it really need all of those dependencies? I know your development > stack is deep here, but maybe I can unwind a bit of the file stuff to > get this in for the next merge window (6.13-rc1) if those two aren't > going to be planned for there. Ah, maybe not. The dependency on files is necessary to allow the file to look at its own fields, e.g. whether O_NONBLOCK is set or what the file position is. But we can take that out for now and add it once both miscdevice and file have landed. I'm hoping that file will land for 6.13, but untangling them allows both to land in 6.13. As for vma, it's needed for mmap, but if I take out the ability to define an mmap operation, I don't need it. We can always add back mmap once both miscdevice and vma have landed. Thank you for the suggestion on untangling the dependencies. > I'll look into this some more next week, thanks! Thanks! Alice
