From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: tracefs splats in lockdown=confidentiality mode Date: Mon, 2 Dec 2019 18:54:26 -0500 Message-ID: <20191202185426.432ca21b@gandalf.local.home> References: <20191101210803.GA9841@xps13.dannf> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Matthew Garrett Cc: dann frazier , Linux Kernel Mailing List , LSM List , Seth Forshee , James Morris , Linux API , Ben Hutchings , Al Viro , Linus Torvalds List-Id: linux-api@vger.kernel.org On Mon, 2 Dec 2019 15:31:52 -0800 Matthew Garrett wrote: > On Fri, Nov 1, 2019 at 2:08 PM dann frazier 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. I think it has to do with ftrace triggering WARN_ON() if it fails to create files. We don't want this to happen if it fails because of lockdown. I'm already looking into it. Thanks! -- Steve