[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1566232996.v8nlwmnjqa.naveen@linux.ibm.com>
Date: Mon, 19 Aug 2019 22:22:12 +0530
From: "Naveen N. Rao" <naveen.n.rao@...ux.ibm.com>
To: Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
Borislav Petkov <bp@...en8.de>,
Catalin Marinas <catalin.marinas@....com>,
"David S. Miller" <davem@...emloft.net>,
"H. Peter Anvin" <hpa@...or.com>,
Jisheng Zhang <Jisheng.Zhang@...aptics.com>,
Masami
Hiramatsu <mhiramat@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
Will Deacon <will@...nel.org>
Cc: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>
Subject: Re: [PATCH 4/4] arm64: implement KPROBES_ON_FTRACE
Jisheng Zhang wrote:
> This patch implements KPROBES_ON_FTRACE for arm64.
>
> ~ # mount -t debugfs debugfs /sys/kernel/debug/
> ~ # cd /sys/kernel/debug/
> /sys/kernel/debug # echo 'p _do_fork' > tracing/kprobe_events
>
> before the patch:
>
> /sys/kernel/debug # cat kprobes/list
> ffffff801009ff7c k _do_fork+0x4 [DISABLED]
This looks wrong -- we should not be allowing kprobe to be registered on
ftrace address without KPROBES_ON_FTRACE. Is _do_fork+0x4 the location
of ftrace entry on arm64?
- Naveen
Powered by blists - more mailing lists