From: Paul Moore <pmoore@redhat.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>,
James Morris <james.l.morris@oracle.com>,
selinux <selinux@tycho.nsa.gov>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: noisy selinux messages on tmpfs mount.
Date: Fri, 09 Jan 2015 15:55:37 -0500 [thread overview]
Message-ID: <6645675.NppomaThWx@sifl> (raw)
In-Reply-To: <20150109191329.GA19400@codemonkey.org.uk>
On Friday, January 09, 2015 02:13:29 PM Dave Jones wrote:
> On Fri, Jan 09, 2015 at 08:06:49AM -0500, Stephen Smalley wrote:
> > 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.
I wonder if this is cron/systemd/whatever creating a new namespace and
mounting a new tmpfs in the namespace? If yes, I wonder if we could limit the
messages to the initial namespace ... ?
--
paul moore
security @ redhat
WARNING: multiple messages have this Message-ID (diff)
From: Paul Moore <pmoore@redhat.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Stephen Smalley <stephen.smalley@gmail.com>,
selinux <selinux@tycho.nsa.gov>,
James Morris <james.l.morris@oracle.com>,
Stephen Smalley <sds@epoch.ncsc.mil>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: noisy selinux messages on tmpfs mount.
Date: Fri, 09 Jan 2015 15:55:37 -0500 [thread overview]
Message-ID: <6645675.NppomaThWx@sifl> (raw)
In-Reply-To: <20150109191329.GA19400@codemonkey.org.uk>
On Friday, January 09, 2015 02:13:29 PM Dave Jones wrote:
> On Fri, Jan 09, 2015 at 08:06:49AM -0500, Stephen Smalley wrote:
> > 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.
I wonder if this is cron/systemd/whatever creating a new namespace and
mounting a new tmpfs in the namespace? If yes, I wonder if we could limit the
messages to the initial namespace ... ?
--
paul moore
security @ redhat
next prev parent reply other threads:[~2015-01-09 20:55 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
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 [this message]
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=6645675.NppomaThWx@sifl \
--to=pmoore@redhat.com \
--cc=davej@codemonkey.org.uk \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@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.