[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8013.1565708810@warthog.procyon.org.uk>
Date: Tue, 13 Aug 2019 16:06:50 +0100
From: David Howells <dhowells@...hat.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: dhowells@...hat.com,
syzbot <syzbot+1e0edc4b8b7494c28450@...kaller.appspotmail.com>,
Eric Biggers <ebiggers@...nel.org>,
David Miller <davem@...emloft.net>,
linux-afs@...ts.infradead.org, LKML <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: kernel BUG at net/rxrpc/local_object.c:LINE!
Dmitry Vyukov <dvyukov@...gle.com> wrote:
> > I meant that I don't know how to turn a tracepoint on from inside the kernel.
>
> This /sys/kernel/debug/tracing/events/rxrpc/rxrpc_local/enable in:
> echo 1 > /sys/kernel/debug/tracing/events/rxrpc/rxrpc_local/enable
> should map to some global variable, right? If so, it should be
> possible to initialize that var to 1 statically. Or that won't work
> for some reason?
As I understand it, it's all hidden inside of tracing macros and ftrace
infrastructure and involves runtime patching the code to enable tracepoints
(they're effectively NOP'ed out when not in use).
So, no, it's not that simple.
I asked Steven and he says:
trace_set_clr_event("sched", "sched_switch", 1);
is the same as
echo 1 > events/sched/sched_switch/enable
So it can be done. Will syzbot actually collect the trace log?
David
Powered by blists - more mailing lists