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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Aug 2021 11:43:52 -0500 From: Ian Pilcher <arequipeno@...il.com> To: Greg KH <gregkh@...uxfoundation.org> Cc: Marek BehĂșn <kabel@...nel.org>, axboe@...nel.dk, kernelnewbies@...nelnewbies.org, linux-kernel@...r.kernel.org, linux-block@...r.kernel.org, pavel@....cz, pali@...nel.org, hch@....de, linux-leds@...r.kernel.org Subject: Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers On 8/10/21 11:24 AM, Greg KH wrote: > There should not be anything "odd" about block devices here, just do > whatever all other LED drivers do when referencing a device. AFAIK, the only LED trigger that does anything similar is the netdev trigger. It uses dev_get_by_name(), which is specific to network devices. The block subsystem doesn't appear to have any similar API, which is why Enzo submitted his patch to export block_class and disk_type back in April[1], when he wanted to do something similar. I'm basically bypassing the need to export the symbols, because my trigger code is actually in the block subsystem, rather than the LEDs subsystem. [1] https://www.spinics.net/lists/linux-leds/msg18244.html -- ======================================================================== In Soviet Russia, Google searches you! ========================================================================
Powered by blists - more mailing lists