linux-kernel - Re: [RFC PATCH] gpio: sysfs: make the sysfs export behavior consistent

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: <CAMRc=Mdt8+ATGVU19E+pRrMhKZTcO49HTPdboHLLeN_Omd6LoQ@mail.gmail.com>
Date: Mon, 30 Sep 2024 09:20:48 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Kent Gibson <warthog618@...il.com>
Cc: Linus Walleij <linus.walleij@...aro.org>, linux-gpio@...r.kernel.org, 
	linux-kernel@...r.kernel.org, 
	Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [RFC PATCH] gpio: sysfs: make the sysfs export behavior consistent

On Mon, Sep 30, 2024 at 3:03 AM Kent Gibson <warthog618@...il.com> wrote:
>
> > I decided to write a sysfs-to-libgpiod compatibility layer based on
> > FUSE. Since Rust is hard, I started prototyping the thing in python
> > first to at least have the logic nailed down before I tackle the rust
> > part.
> >
>
> Something along these lines[1]?
>
> Cheers,
> Kent.
>
> [1]https://dev.to/krjakbrjak/simulating-gpio-sysfs-interface-with-fuse-and-c-30ga
>

Well, this doesn't really do anything. I'm thinking about something
consuming the libgpiod rust bindings to actually be a useful
replacement for kernel sysfs.

The master plan is: provide a drop-in user-space replacement for
sysfs, make users convert to using it instead of the real thing,
eventually remove sysfs from the kernel and then some time after
remove the compatibility layer from existence forcing everybody to now
move to pure libgpiod. :)

Bart