[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACdnJuuXBQ__Sb8=V7CTZfXH=5LfbiU9SmUKapJov3Cd+aHQcw@mail.gmail.com>
Date: Mon, 2 Dec 2019 15:31:52 -0800
From: Matthew Garrett <mjg59@...gle.com>
To: dann frazier <dann.frazier@...onical.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
LSM List <linux-security-module@...r.kernel.org>,
Seth Forshee <seth.forshee@...onical.com>,
James Morris <jmorris@...ei.org>,
Linux API <linux-api@...r.kernel.org>,
Ben Hutchings <ben@...adent.org.uk>,
Al Viro <viro@...iv.linux.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: tracefs splats in lockdown=confidentiality mode
On Fri, Nov 1, 2019 at 2:08 PM dann frazier <dann.frazier@...onical.com> wrote:
> [ 1.763630] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7
This is expected.
> [ 2.913934] ------------[ cut here ]------------
> [ 2.918435] Could not register function stat for cpu 0
> [ 2.923717] WARNING: CPU: 1 PID: 1 at kernel/trace/ftrace.c:987 ftrace_init_tracefs_toplevel+0x168/0x1bc
This is not. I'll look into it.
Powered by blists - more mailing lists