[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16503.1492529434@warthog.procyon.org.uk>
Date: Tue, 18 Apr 2017 16:30:34 +0100
From: David Howells <dhowells@...hat.com>
To: Ben Hutchings <ben@...adent.org.uk>
Cc: dhowells@...hat.com, Andy Shevchenko <andy.shevchenko@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
matthew.garrett@...ula.com, linux-efi@...r.kernel.org,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
acpi4asus-user <acpi4asus-user@...ts.sourceforge.net>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>,
keyrings@...r.kernel.org
Subject: Re: [PATCH 15/24] asus-wmi: Restrict debugfs interface when the kernel is locked down
Ben Hutchings <ben@...adent.org.uk> wrote:
> So it's generally not going to be OK to turn off debugfs. There will
> probably need to be a distinction between believed-safe and unsafe
> directories/files.
Any suggestion on how to mark this distinction? I'd prefer not to modify
every read/write op associated with a debugfs file. Modify
DEFINE_DEBUGFS_ATTRIBUTE() maybe? And provide lockable variants of
debugfs_create_u8() and co.?
David
Powered by blists - more mailing lists