From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757231AbbAHTfK (ORCPT ); Thu, 8 Jan 2015 14:35:10 -0500 Received: from mx1.redhat.com ([209.132.183.28]:58436 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751573AbbAHTfJ (ORCPT ); Thu, 8 Jan 2015 14:35:09 -0500 From: Paul Moore To: Dave Jones , Stephen Smalley Cc: James Morris , Linux Kernel Subject: Re: noisy selinux messages on tmpfs mount. Date: Thu, 08 Jan 2015 14:34:57 -0500 Message-ID: <3227891.DhTeT4XeAv@sifl> Organization: Red Hat User-Agent: KMail/4.14.3 (Linux/3.16.7-gentoo; KDE/4.14.3; x86_64; ; ) In-Reply-To: <20150108190822.GB4365@codemonkey.org.uk> References: <20150108190822.GB4365@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 Thursday, January 08, 2015 02:08:22 PM Dave Jones wrote: > systemd has started mounting a tmpfs in /run/user/ 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. -- paul moore security @ redhat