On Monday, January 12, 2015 09:51:17 AM Christopher J. PeBenito wrote: > On 1/9/2015 3:47 PM, Stephen Smalley wrote: > > On 01/09/2015 02:13 PM, Dave Jones wrote: > >> That doesn't really help with the flooding of dmesg, so no. > >> I should also note that it's not just logging in that creates a new > >> session, it also seems to be getting triggered by cron jobs, or > >> whatever the systemd replacement is. > > > > Fair enough. I think we can likely get rid of it then. > > Are you saying completely get rid of the message in all cases? If so, > how is a user supposed to debug situations where they mount a filesystem > and labeling doesn't work (i.e. no security label support or policy > hasn't been updated for that fs)? I'm pretty sure Stephen just meant the normal case, not the "unknown behavior" case. > Is there going to be another place to look see what the labeling behavior is > for all mounted filesystems? I imagine we could create something in securityfs for that, you want to write a patch Chris? :) -- paul moore security @ redhat _______________________________________________ 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.
