[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c327ecb762ef788ef248ed5c006eeef5afa3b798.camel@decadent.org.uk>
Date: Fri, 11 Oct 2019 20:50:56 +0100
From: Ben Hutchings <ben@...adent.org.uk>
To: Steven Rostedt <rostedt@...dmis.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Matthew Garrett <matthewgarrett@...gle.com>,
James Morris James Morris <jmorris@...ei.org>,
LSM List <linux-security-module@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH] tracefs: Do not allocate and free proxy_ops for lockdown
On Fri, 2019-10-11 at 14:36 -0400, Steven Rostedt wrote:
> On Fri, 11 Oct 2019 11:20:30 -0700
> Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>
> > Willing to do that instead?
>
> Honestly, what you described was my preferred solution ;-)
>
> I just didn't want to upset the lockdown crowd if a new tracefs file
> was opened without doing this.
>
> Once locked down is set, can it ever be undone without rebooting?
[...]
Earlier versions of the lockdown patch set added a magic SysRq command
to turn it off. That's not currently present upstream but there may be
plans to add it.
Ben.
--
Ben Hutchings
It is easier to change the specification to fit the program
than vice versa.
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists