linux-kernel - Re: [RFC PATCH] cmdline: Hide "debug" from /proc/cmdline

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.00.1404030119270.23421@twin.jikos.cz>
Date:	Thu, 3 Apr 2014 01:23:15 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	Mateusz Guzik <mguzik@...hat.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...en8.de>,
	Ingo Molnar <mingo@...nel.org>, Mel Gorman <mgorman@...e.de>,
	Kay Sievers <kay@...y.org>
Subject: Re: [RFC PATCH] cmdline: Hide "debug" from /proc/cmdline

On Wed, 2 Apr 2014, Linus Torvalds wrote:

> Steven, Borislav, one thing that strikes me might be a good idea is to 
> limit the amount of non-kernel noise in dmesg. We already have the 
> concept of rate-limiting various spammy internal kernel messages for 
> when device drivers misbehave etc. Maybe we can just add rate-limiting 
> to the interfaces that add messages to the kernel buffers, and work 
> around this problem that way instead while waiting for Gregs fix to 
> percolate? Or are the systemd debug messages going to so many other 
> places too that that wouldn't really help?

I think that it's in principle a good idea, however ... the in-kernel 
ratelimiting always happens per sourcecode location, but this will be 
rather hard to achieve with interface such as /dev/kmsg.

If /dev/kmsg is going to be ratelimited as a whole, it might potentially 
create a severely unfair situation between individual userspace programs 
trying to do logging (although there is apparently only one userspace 
service doing any logging through this interface whatsoever, right?).

-- 
Jiri Kosina
SUSE Labs

--
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/