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
| ||
|
Date: Sun, 01 Sep 2013 23:48:34 -0500 From: Ian Pilcher <arequipeno@...il.com> To: linux-leds@...r.kernel.org, kernelnewbies@...nelnewbies.org, linux-kernel@...r.kernel.org Subject: Re: device_create_file returns 0 but doesn't work On 09/01/2013 06:38 PM, Ian Pilcher wrote: > I am trying to add an additional sysfs attribute to a device (LED) that > is created by another driver. (My ultimate goal is to provide a way for > a userspace application to use the functionality provided by > led_blink_set, which doesn't currently seem to be possible.) Turns out it is possible, with the LED timer trigger, so this issue is now moot. > > The kernel module code that sets up all the GPIOs & LEDs in my NAS is > at: > > http://pastebin.com/TJZGww8T > > The call to device_create_file is at line 373. > > device_create_file is returning 0, but the "foo" attribute is not being > created. ("find /sys -name '*foo*'" doesn't find anything, so I'm not > just looking in the wrong place.) Still rather odd that it doesn't work, however, since ledtrig-timer.c seems to do pretty much the same thing. Oh well. -- ======================================================================== Ian Pilcher arequipeno@...il.com Sometimes there's nothing left to do but crash and burn...or die trying. ======================================================================== -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists