linux-kernel - Re: noisy selinux messages on tmpfs mount.

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150108193817.GC4365@codemonkey.org.uk>
Date:	Thu, 8 Jan 2015 14:38:17 -0500
From:	Dave Jones <davej@...emonkey.org.uk>
To:	Paul Moore <pmoore@...hat.com>
Cc:	Stephen Smalley <sds@...ho.nsa.gov>,
	James Morris <james.l.morris@...cle.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: noisy selinux messages on tmpfs mount.

On Thu, Jan 08, 2015 at 02:34:57PM -0500, 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.
 
It would help if I had cc'd Stephen's correct email address.
Stephen, for context: https://lkml.org/lkml/2015/1/8/468

I figured there would be pushback from removing it entirely, which is
why I didn't send the obvious patch.

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