We already reduced that message to KERN_DEBUG. Is that not sufficient?
On Thu, Jan 8, 2015 at 2:39 PM, Paul Moore <[email protected]> wrote: > On Thursday, January 08, 2015 02:34:57 PM Paul Moore wrote: >> On Thursday, January 08, 2015 02:08:22 PM Dave Jones wrote: >> > systemd has started mounting a tmpfs in /run/user/<uid> every time a >> > session begins. So after ssh'ing into a box a number of times, dmesg >> > looks like this.. >> > >> > [...] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >> > [...] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >> >> {snip} >> >> > What's a good solution to stopping this spew ? printk_once doesn't seem >> > like a good fit, in case someone is doing different labelling behaviours >> > between mounts. >> > >> > Could we only print it if the mount is being done with non-default >> > behaviour perhaps? >> >> I'm very curious to hear Stephen's opinion on the issue, but I wonder how >> much this would honestly impact us if we removed this message in the case >> where we mount the filesystem with a known labeling behavior. > > [NOTE: adding the SELinux list to the CC line.] > > -- > paul moore > security @ redhat > > _______________________________________________ > Selinux mailing list > [email protected] > To unsubscribe, send email to [email protected]. > To get help, send an email containing "help" to [email protected]. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
