[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10532721.yu8lhX206e@sifl>
Date: Mon, 12 Jan 2015 10:06:43 -0500
From: Paul Moore <pmoore@...hat.com>
To: "Christopher J. PeBenito" <cpebenito@...sys.com>
Cc: Stephen Smalley <sds@...ho.nsa.gov>,
Dave Jones <davej@...emonkey.org.uk>,
Stephen Smalley <stephen.smalley@...il.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 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
--
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/
Powered by blists - more mailing lists