linux-kernel - Re: [PATCH 2/3] leds: add debugfs to device trigger

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:	Sun, 15 Nov 2015 12:22:23 +0100
From:	Pavel Machek <pavel@....cz>
To:	Maciek Borzecki <maciek.borzecki@...il.com>
Cc:	linux-kernel@...r.kernel.org, Richard Purdie <rpurdie@...ys.net>,
	Jacek Anaszewski <j.anaszewski@...sung.com>,
	linux-leds@...r.kernel.org, linux-doc@...r.kernel.org,
	Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH 2/3] leds: add debugfs to device trigger

On Mon 2015-09-28 22:43:04, Maciek Borzecki wrote:
> Add debugfs entries for device activity trigger. Three entries are
> created under /sys/kernel/debug/ledtrig-dev when the driver gets
> loaded. These are:
> 
>   devices - cat'ing will produce a list of currently registered devices
>             in <major>:<minor> format, a line for each device.
> 
>   register - echo'ing <major>:<minor> will create a trigger for this
>              device
> 
>   trigger - echo'ing <major>:<minor> will fire a trigger for this device

Debugfs? Please don't. This is not debugging infrastructure.