From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from goalie.tycho.ncsc.mil (goalie [144.51.242.250]) by tarius.tycho.ncsc.mil (8.14.4/8.14.4) with ESMTP id t09KtmVH003737 for ; Fri, 9 Jan 2015 15:55:48 -0500 From: Paul Moore To: Dave Jones Subject: Re: noisy selinux messages on tmpfs mount. Date: Fri, 09 Jan 2015 15:55:37 -0500 Message-ID: <6645675.NppomaThWx@sifl> In-Reply-To: <20150109191329.GA19400@codemonkey.org.uk> References: <20150108190822.GB4365@codemonkey.org.uk> <20150109191329.GA19400@codemonkey.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Stephen Smalley , James Morris , selinux , Linux Kernel List-Id: "Security-Enhanced Linux \(SELinux\) mailing list" List-Post: List-Help: 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753075AbbAIUzs (ORCPT ); Fri, 9 Jan 2015 15:55:48 -0500 Received: from mx1.redhat.com ([209.132.183.28]:51690 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750998AbbAIUzr (ORCPT ); Fri, 9 Jan 2015 15:55:47 -0500 From: Paul Moore To: Dave Jones Cc: Stephen Smalley , selinux , James Morris , Stephen Smalley , Linux Kernel Subject: Re: noisy selinux messages on tmpfs mount. Date: Fri, 09 Jan 2015 15:55:37 -0500 Message-ID: <6645675.NppomaThWx@sifl> Organization: Red Hat User-Agent: KMail/4.14.3 (Linux/3.16.7-gentoo; KDE/4.14.3; x86_64; ; ) In-Reply-To: <20150109191329.GA19400@codemonkey.org.uk> References: <20150108190822.GB4365@codemonkey.org.uk> <20150109191329.GA19400@codemonkey.org.uk> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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