From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755447AbbAHTIc (ORCPT ); Thu, 8 Jan 2015 14:08:32 -0500 Received: from arcturus.aphlor.org ([188.246.204.175]:53111 "EHLO arcturus.aphlor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750753AbbAHTIa (ORCPT ); Thu, 8 Jan 2015 14:08:30 -0500 Date: Thu, 8 Jan 2015 14:08:22 -0500 From: Dave Jones To: Stephen Smalley Cc: Paul Moore , James Morris , Linux Kernel Subject: noisy selinux messages on tmpfs mount. Message-ID: <20150108190822.GB4365@codemonkey.org.uk> Mail-Followup-To: Dave Jones , Stephen Smalley , Paul Moore , James Morris , Linux Kernel MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Score: -2.9 (--) X-Spam-Report: Spam report generated by SpamAssassin on "arcturus.aphlor.org" Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Authenticated-User: davej@codemonkey.org.uk Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.. [ 929.892760] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 4529.025836] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 8129.170484] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [11729.313034] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [15329.471269] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [18929.613781] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [22529.759596] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [26129.890709] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [26669.001664] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [33328.937304] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [36929.064927] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [40529.178574] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [44129.301952] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [47729.424882] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [51329.287032] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [54929.563390] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [58529.857740] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [62128.992792] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs 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? Dave