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  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]
Date:   Wed, 21 Jul 2021 21:50:07 +0200
From:   Andrew Lunn <>
To:     Marek BehĂșn <>
Cc:     Heiner Kallweit <>,
        Pavel Machek <>,
        Tony Nguyen <>,,, Kurt Kanzenbach <>,,,,,
        Sebastian Andrzej Siewior <>,
        Dvora Fuxbrumer <>,
        "" <>
Subject: Re: [PATCH net-next 5/5] igc: Export LEDs

> Hi Heiner,
> in sysfs, all devices registered under LED class will have symlinks in
> /sys/class/leds. This is how device classes work in Linux.
> There is a standardized format for LED device names, please look at
> Documentation/leds/leds-class.rst.
> Basically the LED name is of the format
>   devicename:color:function

The interesting part here is, what does devicename mean, in this

We cannot use the interface name, because it is not unique, and user
space can change it whenever it wants. So we probably need to build
something around the bus ID, e.g. pci_id. Which is not very friendly


Powered by blists - more mailing lists