netdev - Re: Request for Comment: LED device naming for netdev LEDs

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] [day] [month] [year] [list]

Date:   Wed, 25 Nov 2020 11:59:43 +0100
From:   Pavel Machek <pavel@....cz>
To:     Alexander Dahl <ada@...rsis.com>
Cc:     linux-leds@...r.kernel.org, Marek Behun <marek.behun@....cz>,
        netdev <netdev@...r.kernel.org>,
        David Miller <davem@...emloft.net>,
        Andrew Lunn <andrew@...n.ch>,
        Russell King <linux@...linux.org.uk>,
        Alexander Dahl <post@...pocky.de>
Subject: Re: Request for Comment: LED device naming for netdev LEDs

Hi!

> > > What are your ideas about this problem?
> > > 
> > > Marek
> > 
> > BTW option b) and c) can be usable if we create a new utility, ledtool,
> > to report infromation about LEDs and configure LEDs.
> > 
> > In that case it does not matter if the LED is named
> >   ethernet-adapter0:red:activity
> > or
> >   ethernet-phy0:red:activity
> > because this new ledtool utility could just look deeper into sysfs to
> > find out that the LED corresponds to eth0, whatever it name is.
> 
> I like the idea to have such a tool.  What do you have in mind?  Sounds for me 
> like it would be somehow similar to libgpiod with gpio* for GPIO devices or 
> like libevdev for input devices or like mtd-utils …
> 
> Especially a userspace library could be helpful to avoid reinventing the wheel 
> on userspace developer side?
> 
> Does anyone else know prior work for linux leds sysfs interface from 
> userspace?

I have code in tui project which accesses the LEDs from python... and
I started writing ledtool in rust.

Anyway, I agree we should provide shared library, too. Going through
the fork/exec is just too ugly.

Best regards,
								Pavel
-- 
http://www.livejournal.com/~pavelmachek

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)