All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Paul Moore <pmoore@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	James Morris <james.l.morris@oracle.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: noisy selinux messages on tmpfs mount.
Date: Thu, 8 Jan 2015 14:38:17 -0500	[thread overview]
Message-ID: <20150108193817.GC4365@codemonkey.org.uk> (raw)
In-Reply-To: <3227891.DhTeT4XeAv@sifl>

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

  reply	other threads:[~2015-01-08 19:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 19:08 noisy selinux messages on tmpfs mount Dave Jones
2015-01-08 19:34 ` Paul Moore
2015-01-08 19:38   ` Dave Jones [this message]
2015-01-08 19:39   ` Paul Moore
2015-01-08 19:39     ` Paul Moore
2015-01-09 13:06     ` Stephen Smalley
2015-01-09 13:06       ` Stephen Smalley
2015-01-09 19:13       ` Dave Jones
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:06               ` Paul Moore
2015-01-12 15:53             ` Stephen Smalley
2015-01-09 20:55         ` Paul Moore
2015-01-09 20:55           ` Paul Moore
2015-01-09 21:01           ` Dominick Grift
2015-01-09 21:01             ` Dominick Grift
2015-01-10  3:12             ` Paul Moore
2015-01-10  3:12               ` Paul Moore
2015-01-10  9:11               ` Dominick Grift
2015-01-10  9:11                 ` Dominick Grift
2015-01-10  9:24                 ` 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=20150108193817.GC4365@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@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.