On Apr 28, 2015 8:26 AM, "William Roberts" <[email protected]> wrote: > > > On Apr 28, 2015 8:22 AM, "Stephen Smalley" <[email protected]> wrote: > > > > On 04/28/2015 11:04 AM, William Roberts wrote: > > > > > > On Apr 28, 2015 7:44 AM, "Stephen Smalley" <[email protected] > > > <mailto:[email protected]>> wrote: > > >> I do not know. As per the thread, it can happen any time > > >> device_create_file is called after device_add and the caller does not > > >> explicitly send a uevent. > > >> > > > > > > So kernel authors in sysfs need to explicitly craft and send uevent > > > messages for file adds/dels? Why doesn't the sysfs api take care of this > > > for them, any insight there? > > > > No, I assume it is to avoid storms of such uevents and only generate > > uevents when someone deems them truly necessary. Since Linux > > distributions have not applied fine-grained labeling to most of sysfs to > > date (only selected cases, e.g. for libvirt labeling of nodes owned by > > specific VMs so that they can be accessed by the VM's security context), > > they wouldn't really see this issue. > > It first glance it seems the sysfs, kobject and uevent api (kobject_uevent) are nicely coupled. Were having issues on sys/class/thermal generic driver. I have no clue if this is the source of the problem. Ill post back with results. > > Tai did you ever fix your issue, and how? > > > >
Stephen what's the effort to get option 3 done?
_______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
