Date: Mon, 25 Apr 2016 16:00:05 -0400
From: Steven Rostedt <rostedt@goodmis.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
        Borislav Petkov <bp@alien8.de>,
        Andrew Morton <akpm@linux-foundation.org>,
        Uwe =?UTF-8?B?S2xlaW5lLUvDtm5pZw==?= 
	<u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH v2] printk: Add kernel parameter to disable writes to
 /dev/kmsg
Message-ID: <20160425160005.0eb36aea@gandalf.local.home>
In-Reply-To: <20160425195437.GA25465@kroah.com>
References: <20160425145606.598329f2@gandalf.local.home>
	<20160425190651.GL3448@twins.programming.kicks-ass.net>
	<20160425191815.GA24761@kroah.com>
	<20160425192435.GM3430@twins.programming.kicks-ass.net>
	<20160425195437.GA25465@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 567
Lines: 17

On Mon, 25 Apr 2016 12:54:37 -0700
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:


> > This systemd exposure has seriously eroded your sanity.  
> 
> See Andrew's message, this was added because of klibc :)

For the purpose to pass messages from early init through to final boot.
Systemd continued this for the same purpose. Which I agree is totally
legit. But where systemd fails, is that it continues to use this
interface far beyond the need.

I agree with Andrew, we should have had a way to close the pipe after
the system was up and running.

-- Steve