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>] [day] [month] [year] [list]
Message-ID: <51F2CE21.8030000@linux.intel.com>
Date:	Fri, 26 Jul 2013 12:29:37 -0700
From:	Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: device_register and device_create_file rules


I am aware that it it is always recommended that attributes must be 
associate via attribute groups when calling device_register() .
This way when the device is created, user space can always see 
attributes once they get device create notification via uevent.

I have need to create/delete attributes on fly using 
device_create_file/device_remove_file. In past several drivers did that.

But with the enforcements of device model for new class of drivers, is 
it a big NO? I am not aware of change notification calls other than for 
kobject_uevent.


Thanks,
Srinivas





--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ