From: Paul Moore <pmoore@redhat.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Dave Jones <davej@codemonkey.org.uk>,
Stephen Smalley <stephen.smalley@gmail.com>,
selinux <selinux@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: Mon, 12 Jan 2015 10:06:43 -0500 [thread overview]
Message-ID: <10532721.yu8lhX206e@sifl> (raw)
In-Reply-To: <54B3DF65.809@tresys.com>
On Monday, January 12, 2015 09:51:17 AM Christopher J. PeBenito wrote:
> On 1/9/2015 3:47 PM, Stephen Smalley wrote:
> > On 01/09/2015 02:13 PM, Dave Jones wrote:
> >> 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.
>
> Are you saying completely get rid of the message in all cases? If so,
> how is a user supposed to debug situations where they mount a filesystem
> and labeling doesn't work (i.e. no security label support or policy
> hasn't been updated for that fs)?
I'm pretty sure Stephen just meant the normal case, not the "unknown behavior"
case.
> Is there going to be another place to look see what the labeling behavior is
> for all mounted filesystems?
I imagine we could create something in securityfs for that, you want to write
a patch Chris? :)
--
paul moore
security @ redhat
next prev parent reply other threads:[~2015-01-12 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 19:08 Dave Jones
2015-01-08 19:34 ` 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 [this message]
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=10532721.yu8lhX206e@sifl \
--to=pmoore@redhat.com \
--cc=cpebenito@tresys.com \
--cc=davej@codemonkey.org.uk \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=stephen.smalley@gmail.com \
/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
all inboxes | Powered by JetHome®