[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240129181528.2aa5e39f@gandalf.local.home>
Date: Mon, 29 Jan 2024 18:15:28 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: kernel test robot <oliver.sang@...el.com>, oe-lkp@...ts.linux.dev,
lkp@...el.com, linux-kernel@...r.kernel.org, Masami Hiramatsu
<mhiramat@...nel.org>, Mark Rutland <mark.rutland@....com>, Mathieu
Desnoyers <mathieu.desnoyers@...icios.com>, Christian Brauner
<brauner@...nel.org>, Al Viro <viro@...iv.linux.org.uk>, Ajay Kaher
<ajay.kaher@...adcom.com>, linux-trace-kernel@...r.kernel.org
Subject: Re: [linus:master] [eventfs] 852e46e239:
BUG:unable_to_handle_page_fault_for_address
On Mon, 29 Jan 2024 17:47:32 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:
> > And I hope there aren't any other stupid things I missed like that.
>
> Well the preliminary tests pass with this added to your patch:
Spoke too soon. The later tests started failing.
It fails on creating a kprobe, deleting it, and then recreating it. Even
though the directory is there, it can't be accessed.
# cd /sys/kernel/tracing
// Create a kprobe
# echo 'p:sched schedule' >> kprobe_events
# ls events/kprobes/
enable filter sched
// Now delete the kprobe
# echo '-:sched schedule' >> kprobe_events
// Make sure it's gone
# ls events/kprobes/
ls: cannot access 'events/kprobes/': No such file or directory
// Recreate it
# echo 'p:sched schedule' >> kprobe_events
# ls events/kprobes/
ls: cannot access 'events/kprobes/': No such file or directory
# ls events | grep kprobes
kprobes
No longer able to access it.
# ls -l events | grep kprobes
ls: cannot access 'events/kprobes': No such file or directory
d????????? ? ? ? ? ? kprobes
-- Steve
Powered by blists - more mailing lists