On Fri, May 22, 2015 at 11:25:35AM -0700, william.c.roberts@xxxxxxxxx wrote: > From: William Roberts <william.c.roberts@xxxxxxxxx> > > On the Android side of the house, were required to label each and > every sysfs file with a specific label. "required"? And what label are you having to use? > sysfs often has transient > files, and this uncovered a limitation in SELinux. In most filesystems > the new inode inherits from the parents label, but in sysfs, this > was not the case. The new inode would inherit the syfs wide "default" > label. Do you really want to build up a list of SELinux policies for sysfs files/directories, only to see them need to be redone when the tree moves things around in the future? What type of "rules" are you using here for sysfs to handle the dynamic-ness of the tree properly? thanks, greg k-h _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
