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]

Date:	Fri, 09 Jan 2015 15:47:01 -0500
From:	Stephen Smalley <sds@...ho.nsa.gov>
To:	Dave Jones <davej@...emonkey.org.uk>,
	Stephen Smalley <stephen.smalley@...il.com>,
	Paul Moore <pmoore@...hat.com>,
	selinux <selinux@...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 01/09/2015 02:13 PM, Dave Jones wrote:
> On Fri, Jan 09, 2015 at 08:06:49AM -0500, Stephen Smalley wrote:
>  
>  > On Thu, Jan 8, 2015 at 2:39 PM, Paul Moore <pmoore@...hat.com> 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.
>  >
>  > We already reduced that message to KERN_DEBUG.  Is that not sufficient?
> 
> 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.
--
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/