Date: Tue, 26 Apr 2016 15:47:42 -0400
From: Steven Rostedt <rostedt@goodmis.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Ingo Molnar <mingo@kernel.org>, Peter Zijlstra <peterz@infradead.org>,
        Borislav Petkov <bp@alien8.de>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: printk: Add kernel parameter to disable writes to /dev/kmsg
Message-ID: <20160426154742.0da764a9@gandalf.local.home>
In-Reply-To: <20160426184458.GB8162@amd>
References: <20160425130629.188a901c@gandalf.local.home>
	<20160426184458.GB8162@amd>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 544
Lines: 14

On Tue, 26 Apr 2016 20:44:58 +0200
Pavel Machek <pavel@ucw.cz> wrote:

> > I simply propose a way to let us kernel developers keep user space from
> > interfering, by adding a new kernel command line parameter that will
> > disable writing to /dev/kmsg. Any attempt to open the file in write
> > mode will return a -EPERM error.  
> 
> chmod 400 /dev/kmsg? With udev, it should be possible to make it persistent...

But this opened while initramdisk is used. I'm thinking this wont work,
or does udev run before main root is mounted?

-- Steve