From: Dave Jones <davej@codemonkey.org.uk>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Paul Moore <pmoore@redhat.com>,
James Morris <james.l.morris@oracle.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: noisy selinux messages on tmpfs mount.
Date: Thu, 8 Jan 2015 14:08:22 -0500 [thread overview]
Message-ID: <20150108190822.GB4365@codemonkey.org.uk> (raw)
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..
[ 929.892760] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 4529.025836] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 8129.170484] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[11729.313034] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[15329.471269] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[18929.613781] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[22529.759596] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[26129.890709] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[26669.001664] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[33328.937304] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[36929.064927] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[40529.178574] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[44129.301952] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[47729.424882] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[51329.287032] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[54929.563390] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[58529.857740] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[62128.992792] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
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?
Dave
next reply other threads:[~2015-01-08 19:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 19:08 Dave Jones [this message]
2015-01-08 19:34 ` noisy selinux messages on tmpfs mount Paul Moore
2015-01-08 19:38 ` Dave Jones
2015-01-08 19:39 ` Paul Moore
2015-01-09 13:06 ` Stephen Smalley
2015-01-09 19:13 ` Dave Jones
2015-01-09 20:47 ` Stephen Smalley
2015-01-12 14:51 ` Christopher J. PeBenito
2015-01-12 15:06 ` Paul Moore
2015-01-12 15:53 ` Stephen Smalley
2015-01-09 20:55 ` Paul Moore
2015-01-09 21:01 ` Dominick Grift
2015-01-10 3:12 ` Paul Moore
2015-01-10 9:11 ` Dominick Grift
2015-01-10 9:24 ` Dominick Grift
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150108190822.GB4365@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmoore@redhat.com \
--cc=sds@epoch.ncsc.mil \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox