tracing: wprobe: Add wprobe for watchpoint
Subsystems (7)
Masami Hiramatsu (Google)
maintainerv5 cover tracing: wprobe: Add wprobe for watchpoint
Hi,
Here is the 5th version of the series for adding new wprobe (watch probe) which provides memory access tracing event. Moreover, this can be used via event trigger. Thus it can trace memory access on a dynamically allocated objects too.
The previous version is here:
https://lore.kernel.org/all/175785897434.234168.6798590787777427098.stgit@devnote2/
This version updates the document about wprobe according to Randy's comment and modify config for test cases.
This still include Jinchao's x86 HWBP patches[1][2] as [2/8][3/8].
[1] https://lore.kernel.org/all/[email protected]/
[2] https://lore.kernel.org/all/[email protected]/
Usage
-----
The basic usage of this wprobe is similar to other probes;
w:[GRP/][EVENT] [r|w|rw]@<ADDRESS|SYMBOL[+OFFS]> [FETCHARGS]
This defines a new wprobe event. For example, to trace jiffies update, you can do;
echo 'w:my_jiffies w@jiffies:8 value=+0($addr)' >> dynamic_events echo 1 > events/wprobes/my_jiffies/enable
Moreover, this can be combined with event trigger to trace the memory accecss on slab objects. The trigger syntax is;
set_wprobe:WPROBE_EVENT:FIELD[+OFFSET] [if FILTER] clear_wprobe:WPROBE_EVENT[:FIELD[+OFFSET]] [if FILTER]
set_wprobe sets WPROBE_EVENT's watch address on FIELD[+OFFSET]. clear_wprobe clears WPROBE_EVENT's watch address if it is set to FIELD[+OFFSET]. If FIELD is omitted, forcibly clear the watch address when trigger event is hit.
For example, trace the first 8 byte of the dentry data structure passed to do_truncate() until it is deleted by __dentry_kill(). (Note: all tracefs setup uses '>>' so that it does not kick do_truncate())
# echo 'w:watch rw@0:8 address=$addr value=+0($addr)' > dynamic_events
# echo 'f:truncate do_truncate dentry=$arg2' >> dynamic_events # echo 'set_wprobe:watch:dentry' >> events/fprobes/truncate/trigger
# echo 'f:dentry_kill __dentry_kill dentry=$arg1' >> dynamic_events # echo 'clear_wprobe:watch:dentry' >> events/fprobes/dentry_kill/trigger
# echo 1 >> events/fprobes/truncate/enable # echo 1 >> events/fprobes/dentry_kill/enable
# echo aaa > /tmp/hoge # echo bbb > /tmp/hoge # echo ccc > /tmp/hoge # rm /tmp/hoge
Then, the trace data will show;
# tracer: nop
#
# entries-in-buffer/entries-written: 16/16 #P:8
#
# _-----=> irqs-off/BH-disabled
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / _-=> migrate-disable
# |||| / delay
# TASK-PID CPU# ||||| TIMESTAMP FUNCTION
# | | | ||||| | |
sh-113 [004] ..... 6.467444: truncate: (do_truncate+0x4/0x120) dentry=0xffff8880044f0fd8
sh-113 [004] ..Zff 6.468534: watch: (lookup_fast+0xaa/0x150) address=0xffff8880044f0fd8 value=0x200080
sh-113 [004] ..Zff 6.468542: watch: (step_into+0x82/0x360) address=0xffff8880044f0fd8 value=0x200080
sh-113 [004] ..Zff 6.468547: watch: (step_into+0x9f/0x360) address=0xffff8880044f0fd8 value=0x200080
sh-113 [004] ..Zff 6.468553: watch: (path_openat+0xb3a/0xe70) address=0xffff8880044f0fd8 value=0x200080
sh-113 [004] ..Zff 6.468557: watch: (path_openat+0xb9a/0xe70) address=0xffff8880044f0fd8 value=0x200080
sh-113 [004] ..... 6.468563: truncate: (do_truncate+0x4/0x120) dentry=0xffff8880044f0fd8
sh-113 [004] ...1. 6.469826: dentry_kill: (__dentry_kill+0x0/0x220) dentry=0xffff8880044f0ea0
sh-113 [004] ...1. 6.469859: dentry_kill: (__dentry_kill+0x0/0x220) dentry=0xffff8880044f0d68
rm-118 [001] ..Zff 6.472360: watch: (lookup_fast+0xaa/0x150) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] ..Zff 6.472366: watch: (step_into+0x82/0x360) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] ..Zff 6.472370: watch: (step_into+0x9f/0x360) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] ..Zff 6.472386: watch: (lookup_fast+0xaa/0x150) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] ..Zff 6.472390: watch: (step_into+0x82/0x360) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] ..Zff 6.472394: watch: (step_into+0x9f/0x360) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] ..Zff 6.472415: watch: (lookup_one_qstr_excl+0x2c/0x150) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] ..Zff 6.472419: watch: (lookup_one_qstr_excl+0xd5/0x150) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] ..Zff 6.472424: watch: (may_delete+0x18/0x200) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] ..Zff 6.472428: watch: (may_delete+0x194/0x200) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] ..Zff 6.472446: watch: (vfs_unlink+0x63/0x1c0) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] d.Z.. 6.472528: watch: (dont_mount+0x19/0x30) address=0xffff8880044f0fd8 value=0x200180
rm-118 [001] ..Zff 6.472533: watch: (vfs_unlink+0x11a/0x1c0) address=0xffff8880044f0fd8 value=0x200180
rm-118 [001] ..Zff 6.472538: watch: (vfs_unlink+0x12e/0x1c0) address=0xffff8880044f0fd8 value=0x200180
rm-118 [001] d.Z1. 6.472543: watch: (d_delete+0x61/0xa0) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] d.Z1. 6.472547: watch: (dentry_unlink_inode+0x14/0x110) address=0xffff8880044f0fd8 value=0x200080
rm-118 [001] d.Z1. 6.472551: watch: (dentry_unlink_inode+0x1e/0x110) address=0xffff8880044f0fd8 value=0x80
rm-118 [001] d.Z.. 6.472563: watch: (fast_dput+0x8d/0x120) address=0xffff8880044f0fd8 value=0x80
rm-118 [001] ...1. 6.472567: dentry_kill: (__dentry_kill+0x0/0x220) dentry=0xffff8880044f0fd8
sh-113 [004] ...2. 6.473049: dentry_kill: (__dentry_kill+0x0/0x220) dentry=0xffff888006e383a8Thank you,
---
Jinchao Wang (2):
x86/hw_breakpoint: Unify breakpoint install/uninstall x86/hw_breakpoint: Add arch_reinstall_hw_breakpoint
Masami Hiramatsu (Google) (6):
tracing: wprobe: Add watchpoint probe event based on hardware breakpoint
HWBP: Add modify_wide_hw_breakpoint_local() API
tracing: wprobe: Add wprobe event trigger
selftests: tracing: Add a basic testcase for wprobe
selftests: tracing: Add syntax testcase for wprobe
selftests: ftrace: Add wprobe trigger testcase
Documentation/trace/index.rst | 1 Documentation/trace/wprobetrace.rst | 155 +++ arch/Kconfig | 10 arch/x86/Kconfig | 1 arch/x86/include/asm/hw_breakpoint.h | 8 arch/x86/kernel/hw_breakpoint.c | 148 ++- include/linux/hw_breakpoint.h | 6 include/linux/trace_events.h | 3 kernel/events/hw_breakpoint.c | 37 + kernel/trace/Kconfig | 23 kernel/trace/Makefile | 1 kernel/trace/trace.c | 9 kernel/trace/trace.h | 5 kernel/trace/trace_probe.c | 22 kernel/trace/trace_probe.h | 8 kernel/trace/trace_wprobe.c | 1115 ++++++++++++++++++++ tools/testing/selftests/ftrace/config | 2 .../ftrace/test.d/dynevent/add_remove_wprobe.tc | 68 + .../test.d/dynevent/wprobes_syntax_errors.tc | 20 .../ftrace/test.d/trigger/trigger-wprobe.tc | 48 + 20 files changed, 1625 insertions(+), 65 deletions(-) create mode 100644 Documentation/trace/wprobetrace.rst create mode 100644 kernel/trace/trace_wprobe.c create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/add_remove_wprobe.tc create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/wprobes_syntax_errors.tc create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/trigger-wprobe.tc
--
Masami Hiramatsu (Google) <[email protected]>
Masami Hiramatsu (Google)
maintainerPATCH v5 1/8 tracing: wprobe: Add watchpoint probe event based on hardware breakpoint
From: Masami Hiramatsu (Google) <[email protected]>
Add a new probe event for the hardware breakpoint called wprobe-event. This wprobe allows user to trace (watch) the memory access at the specified memory address.
The new syntax is;
w[:[GROUP/]EVENT] [r|w|rw]@[ADDR|SYM][:SIZE] [FETCH_ARGs]
User also can use $addr to fetch the accessed address. But no other variables are supported. To record updated value, use '+0($addr)'.
For example, tracing updates of the jiffies;
/sys/kernel/tracing # echo 'w:my_jiffies w@jiffies' >> dynamic_events /sys/kernel/tracing # cat dynamic_events w:wprobes/my_jiffies w@jiffies:4
/sys/kernel/tracing # echo 1 > events/wprobes/my_jiffies/enable /sys/kernel/tracing # head -n 20 trace | tail -n 5
# TASK-PID CPU# ||||| TIMESTAMP FUNCTION
# | | | ||||| | |
<idle>-0 [000] d.Z1. 206.547317: my_jiffies: (tick_do_update_jiffies64+0xbe/0x130)
<idle>-0 [000] d.Z1. 206.548341: my_jiffies: (tick_do_update_jiffies64+0xbe/0x130)
<idle>-0 [000] d.Z1. 206.549346: my_jiffies: (tick_do_update_jiffies64+0xbe/0x130)---
Changes in v5:
- The documentation and comments have been revised accordingly.
- default y has been removed.
Changes in v3:
- Enclose the register-API dependent code in trace_probe.c with CONFIG_HAVE_FUNCTION_ARG_ACCESS_API.
--- Documentation/trace/index.rst | 1 Documentation/trace/wprobetrace.rst | 69 ++++ include/linux/trace_events.h | 2 kernel/trace/Kconfig | 13 + kernel/trace/Makefile | 1 kernel/trace/trace.c | 9 kernel/trace/trace.h | 5 kernel/trace/trace_probe.c | 22 + kernel/trace/trace_probe.h | 8 kernel/trace/trace_wprobe.c | 685 +++++++++++++++++++++++++++++++++++ 10 files changed, 812 insertions(+), 3 deletions(-) create mode 100644 Documentation/trace/wprobetrace.rst create mode 100644 kernel/trace/trace_wprobe.c
Documentation/trace/index.rst +1 -0
@@ -36,6 +36,7 @@ the Linux kernel. kprobes kprobetrace fprobetrace + wprobetrace eprobetrace fprobe ring-buffer-design
Documentation/trace/wprobetrace.rst new file +69 -0
69 lines not on this page · raw message
include/linux/trace_events.h +2 -0
@@ -324,6 +324,7 @@ enum {TRACE_EVENT_FL_UPROBE_BIT ,TRACE_EVENT_FL_EPROBE_BIT ,TRACE_EVENT_FL_FPROBE_BIT , +TRACE_EVENT_FL_WPROBE_BIT ,TRACE_EVENT_FL_CUSTOM_BIT , TRACE_EVENT_FL_TEST_STR_BIT, };
@@ -354,6 +355,7 @@ enum {TRACE_EVENT_FL_UPROBE = (1 <<TRACE_EVENT_FL_UPROBE_BIT ),TRACE_EVENT_FL_EPROBE = (1 <<TRACE_EVENT_FL_EPROBE_BIT ),TRACE_EVENT_FL_FPROBE = (1 <<TRACE_EVENT_FL_FPROBE_BIT ), +TRACE_EVENT_FL_WPROBE = (1 <<TRACE_EVENT_FL_WPROBE_BIT ),TRACE_EVENT_FL_CUSTOM = (1 <<TRACE_EVENT_FL_CUSTOM_BIT ), TRACE_EVENT_FL_TEST_STR = (1 << TRACE_EVENT_FL_TEST_STR_BIT), };
kernel/trace/Kconfig +13 -0
@@ -807,6 +807,19 @@ config EPROBE_EVENTS convert the type of an event field. For example, turn an address into a string. +config WPROBE_EVENTS + bool "Enable wprobe-based dynamic events" + depends on TRACING + depends on HAVE_HW_BREAKPOINT + select PROBE_EVENTS + select DYNAMIC_EVENTS + help + This allows the user to add watchpoint tracing events based on + hardware breakpoints on the fly via the ftrace interface. + + Those events can be inserted wherever hardware breakpoints can be + set, and record accessed memory address and values. + config BPF_EVENTS depends on BPF_SYSCALL depends on (KPROBE_EVENTS || UPROBE_EVENTS) && PERF_EVENTS
kernel/trace/Makefile +1 -0
@@ -106,6 +106,7 @@ obj-$(CONFIG_FTRACE_RECORD_RECURSION) += trace_recursion_record.o obj-$(CONFIG_FPROBE) += fprobe.o obj-$(CONFIG_RETHOOK) += rethook.o obj-$(CONFIG_FPROBE_EVENTS) += trace_fprobe.o +obj-$(CONFIG_WPROBE_EVENTS) += trace_wprobe.o obj-$(CONFIG_TRACEPOINT_BENCHMARK) += trace_benchmark.o obj-$(CONFIG_RV) += rv/
kernel/trace/trace.c +8 -1
@@ -5506,8 +5506,12 @@ static const char readme_msg[] =" uprobe_events\t\t- Create/append/remove/show the userspace dynamic events\n" "\t\t\t Write into this file to define/undefine new trace events.\n"#endif +#ifdef CONFIG_WPROBE_EVENTS +" wprobe_events\t\t- Create/append/remove/show the hardware breakpoint dynamic events\n" + "\t\t\t Write into this file to define/undefine new trace events.\n" +#endif #if defined(CONFIG_KPROBE_EVENTS ) || defined(CONFIG_UPROBE_EVENTS ) || \ - defined(CONFIG_FPROBE_EVENTS ) + defined(CONFIG_FPROBE_EVENTS ) || defined(CONFIG_WPROBE_EVENTS ) "\t accepts: event-definitions (one definition per line)\n"#if defined(CONFIG_KPROBE_EVENTS ) || defined(CONFIG_UPROBE_EVENTS )"\t Format: p[:[<group>/][<event>]] <place> [<args>]\n"
@@ -5517,6 +5521,9 @@ static const char readme_msg[] ="\t f[:[<group>/][<event>]] <func-name>[%return] [<args>]\n" "\t t[:[<group>/][<event>]] <tracepoint> [<args>]\n"#endif +#ifdef CONFIG_WPROBE_EVENTS + "\t w[:[<group>/][<event>]] [r|w|rw]@<addr>[:<len>]\n" +#endif #ifdef CONFIG_HIST_TRIGGERS "\t s:[synthetic/]<event> <field> [<field>]\n"#endif
kernel/trace/trace.h +5 -0
@@ -173,6 +173,11 @@ struct fexit_trace_entry_head {unsigned long ret_ip; }; +struct wprobe_trace_entry_head { +struct trace_entry ent; +unsigned long ip; +}; +#define TRACE_BUF_SIZE 1024struct trace_array ;
kernel/trace/trace_probe.c +21 -1
@@ -968,6 +968,24 @@ static int parse_probe_vars(char *orig_arg, const struct fetch_type *t, goto inval; } +/* wprobe only support "$addr" and "$value" variable */ +if (ctx->flags &TPARG_FL_WPROBE ) { +if (!strcmp (arg,"addr" )) { + code->op =FETCH_OP_BADDR ; +return 0 ; + } +if (!strcmp (arg,"value" )) { + code->op =FETCH_OP_BADDR ; + code++; + code->op =FETCH_OP_DEREF ; + code->offset =0 ; + *pcode = code; +return 0 ; + } + err =TP_ERR_BAD_VAR ; + goto inval; + } +if (str_has_prefix (arg,"retval" )) {if (!(ctx->flags &TPARG_FL_RETURN )) { err =TP_ERR_RETVAL_ON_PROBE ;
@@ -1097,8 +1115,9 @@ parse_probe_arg(char *arg, const struct fetch_type *type, ret =parse_probe_vars (arg, type, pcode, end, ctx);break ; +#ifdef CONFIG_HAVE_FUNCTION_ARG_ACCESS_API case '%' :/* named register */ -if (ctx->flags & (TPARG_FL_TEVENT |TPARG_FL_FPROBE )) { +if (ctx->flags & (TPARG_FL_TEVENT |TPARG_FL_FPROBE |TPARG_FL_WPROBE )) {/* eprobe and fprobe do not handle registers */ trace_probe_log_err (ctx->offset,BAD_VAR );break ;
@@ -1111,6 +1130,7 @@ parse_probe_arg(char *arg, const struct fetch_type *type, } elsetrace_probe_log_err (ctx->offset,BAD_REG_NAME );break ; +#endif case '@' :/* memory, file-offset or symbol */ if (isdigit (arg[1 ])) {
kernel/trace/trace_probe.h +7 -1
@@ -89,6 +89,7 @@ enum fetch_op {FETCH_OP_STACK ,/* Stack : .param = index */ FETCH_OP_STACKP ,/* Stack pointer */ FETCH_OP_RETVAL ,/* Return value */ +FETCH_OP_BADDR ,/* Break address */ FETCH_OP_IMM ,/* Immediate : .immediate */ FETCH_OP_COMM ,/* Current comm */ FETCH_OP_ARG, /* Function argument : .param */
@@ -396,6 +397,7 @@ static inline int traceprobe_get_entry_data_size(struct trace_probe *tp)#define TPARG_FL_USER BIT(4)#define TPARG_FL_FPROBE BIT(5)#define TPARG_FL_TPOINT BIT(6) +#define TPARG_FL_WPROBE BIT(7)#define TPARG_FL_LOC_MASK GENMASK(4, 0)static inline bool tparg_is_function_entry (unsigned int flags)
@@ -556,7 +558,11 @@ extern int traceprobe_define_arg_fields(struct trace_event_call *event_call,C (BAD_TYPE4STR ,"This type does not fit for string." ),\C (NEED_STRING_TYPE ,"$comm and immediate-string only accepts string type" ),\C (TOO_MANY_ARGS ,"Too many arguments are specified" ), \ -C (TOO_MANY_EARGS ,"Too many entry arguments specified" ), +C (TOO_MANY_EARGS ,"Too many entry arguments specified" ), \ +C (BAD_ACCESS_FMT ,"Access memory address requires @" ), \ +C (BAD_ACCESS_TYPE ,"Bad memory access type" ), \ +C (BAD_ACCESS_LEN ,"This memory access length is not supported" ), \ +C (BAD_ACCESS_ADDR ,"Invalid access memory address" ), #undef C #define C(a, b) TP_ERR_##a
kernel/trace/trace_wprobe.c new file +685 -0
685 lines not on this page · raw message
Masami Hiramatsu (Google)
maintainerRe: [PATCH v5 1/8] tracing: wprobe: Add watchpoint probe event based on hardware breakpoint
Quoted 19 lines · On Tue, 23 Sep 2025 10:16:51 +0900 "Masami Hiramatsu (Google)"…
From: Masami Hiramatsu (Google) <[email protected]>
Add a new probe event for the hardware breakpoint called wprobe-event. This wprobe allows user to trace (watch) the memory access at the specified memory address.
The new syntax is;w[:[GROUP/]EVENT] [r|w|rw]@[ADDR|SYM][:SIZE] [
FETCH_ARGs]User also can use $addr to fetch the accessed address. But no other variables are supported. To record updated value, use '+0($addr)'.
For example, tracing updates of the jiffies;
/sys/kernel/tracing# echo 'w:my_jiffies w@jiffies' >>dynamic_events/sys/kernel/tracing# catdynamic_eventsw:wprobes/my_jiffies w@jiffies:4
/sys/kernel/tracing# echo 1 > events/wprobes/my_jiffies/enable/sys/kernel/tracing# head -n 20 trace | tail -n 5
Quoted 6 lines
# TASK-PID CPU# ||||| TIMESTAMP FUNCTION
# | | | ||||| | |
<idle>-0 [000] d.Z1. 206.547317: my_jiffies: (tick_do_update_jiffies64+0xbe/0x130)
<idle>-0 [000] d.Z1. 206.548341: my_jiffies: (tick_do_update_jiffies64+0xbe/0x130)
<idle>-0 [000] d.Z1. 206.549346: my_jiffies: (tick_do_update_jiffies64+0xbe/0x130)Let me pick this patch to probe/for-next. But others depends on x86 and hw_breakpoint specific changes([2/8]-[4/8]), I need Peter's Ack.
Thank you,
Quoted 984 lines
Signed-off-by Masami Hiramatsu (Google) <[email protected]>---
Changes in v5:
- The documentation and comments have been revised accordingly.
-default yhas been removed.
Changes in v3:
- Enclose the register-API dependent code intrace_probe.cwithCONFIG_HAVE_FUNCTION_ARG_ACCESS_API.--- Documentation/trace/index.rst | 1 Documentation/trace/wprobetrace.rst | 69 ++++ include/linux/trace_events.h | 2 kernel/trace/Kconfig | 13 + kernel/trace/Makefile | 1 kernel/trace/trace.c | 9 kernel/trace/trace.h | 5 kernel/trace/trace_probe.c | 22 + kernel/trace/trace_probe.h | 8 kernel/trace/trace_wprobe.c | 685 +++++++++++++++++++++++++++++++++++ 10 files changed, 812 insertions(+), 3 deletions(-) create mode 100644 Documentation/trace/wprobetrace.rst create mode 100644 kernel/trace/trace_wprobe.cDocumentation/trace/index.rst +1
-0@@ -36,6 +36,7 @@ the Linux kernel. kprobes kprobetrace fprobetrace + wprobetrace eprobetrace fprobe ring-buffer-designDocumentation/trace/wprobetrace.rst new file +69
-0@@ -0,0 +1,69 @@ +.. SPDX-License-Identifier: GPL-2.0 + +======================================= +Watchpoint probe (wprobe) Event Tracing +======================================= + +.. Author: Masami Hiramatsu <[email protected]> + +Overview +-------- + +Wprobe event is a dynamic event based on the hardware breakpoint, which is +similar to other probe events, but it is for watching data access. It allows +you to trace which code accesses a specified data. + +As same as other dynamic events, wprobe events are defined via +`dynamic_events` interface file on tracefs. + +Synopsis of wprobe-events +------------------------- +:: + + w:[GRP/][EVENT] SPEC [FETCHARGS] : Probe on data access + + GRP : Group name for wprobe. If omitted, use "wprobes" for it. + EVENT : Event name for wprobe. If omitted, an event name is + generated based on the address or symbol. + SPEC : Breakpoint specification. + [r|w|rw]@<ADDRESS|SYMBOL[+|-OFFS]>[:LENGTH] + + r|w|rw : Access type, r for read, w for write, and rw for both. + Default is rw if omitted. + ADDRESS : Address to trace (hexadecimal). + SYMBOL : Symbol name to trace. + LENGTH : Length of the data to trace in bytes. (1, 2, 4, or 8) + + FETCHARGS : Arguments. Each probe can have up to 128 args. + $addr : Fetch the accessing address. + @ADDR : Fetch memory at ADDR (ADDR should be in kernel) + @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol) + +|-[u]OFFS(FETCHARG) : Fetch memory at FETCHARG +|- OFFS address.(\*1)(\*2) + \IMM : Store an immediate value to the argument. + NAME=FETCHARG : Set NAME as the argument name of FETCHARG. + FETCHARG:TYPE : Set TYPE as the type of FETCHARG. Currently, basic types + (u8/u16/u32/u64/s8/s16/s32/s64), hexadecimal types + (x8/x16/x32/x64), "char", "string", "ustring", "symbol", "symstr" + and bitfield are supported. + + (\*1) this is useful for fetching a field of data structures. + (\*2) "u" means user-space dereference. + +For the details of TYPE, see :ref:`kprobetrace documentation <kprobetrace_types>`. + +Usage examples +-------------- +Here is an example to add a wprobe event on a variable `jiffies`. +:: + + # echo 'w:my_jiffies w@jiffies' >> dynamic_events + # cat dynamic_events + w:wprobes/my_jiffies w@jiffies + # echo 1 > events/wprobes/enable + # cat trace | head + # TASK-PID CPU# ||||| TIMESTAMP FUNCTION + # | | | ||||| | | + <idle>-0 [000] d.Z1. 717.026259: my_jiffies: (tick_do_update_jiffies64+0xbe/0x130) + <idle>-0 [000] d.Z1. 717.026373: my_jiffies: (tick_do_update_jiffies64+0xbe/0x130) + +You can see the code which writes to `jiffies` is `tick_do_update_jiffies64()`.include/linux/trace_events.h +2
-0@@ -324,6 +324,7 @@ enum {TRACE_EVENT_FL_UPROBE_BIT ,TRACE_EVENT_FL_EPROBE_BIT ,TRACE_EVENT_FL_FPROBE_BIT , +TRACE_EVENT_FL_WPROBE_BIT ,TRACE_EVENT_FL_CUSTOM_BIT , TRACE_EVENT_FL_TEST_STR_BIT, };@@ -354,6 +355,7 @@ enum {TRACE_EVENT_FL_UPROBE = (1 <<TRACE_EVENT_FL_UPROBE_BIT ),TRACE_EVENT_FL_EPROBE = (1 <<TRACE_EVENT_FL_EPROBE_BIT ),TRACE_EVENT_FL_FPROBE = (1 <<TRACE_EVENT_FL_FPROBE_BIT ), +TRACE_EVENT_FL_WPROBE = (1 <<TRACE_EVENT_FL_WPROBE_BIT ),TRACE_EVENT_FL_CUSTOM = (1 <<TRACE_EVENT_FL_CUSTOM_BIT ), TRACE_EVENT_FL_TEST_STR = (1 << TRACE_EVENT_FL_TEST_STR_BIT), };kernel/trace/Kconfig +13
-0@@ -807,6 +807,19 @@ config EPROBE_EVENTS convert the type of an event field. For example, turn an address into a string. +config WPROBE_EVENTS + bool "Enable wprobe-based dynamic events" + depends on TRACING + depends on HAVE_HW_BREAKPOINT + select PROBE_EVENTS + select DYNAMIC_EVENTS + help + This allows the user to add watchpoint tracing events based on + hardware breakpoints on the fly via the ftrace interface. + + Those events can be inserted wherever hardware breakpoints can be + set, and record accessed memory address and values. + config BPF_EVENTS depends on BPF_SYSCALL depends on (KPROBE_EVENTS || UPROBE_EVENTS) && PERF_EVENTSkernel/trace/Makefile +1
-0@@ -106,6 +106,7 @@ obj-$(CONFIG_FTRACE_RECORD_RECURSION) += trace_recursion_record.o obj-$(CONFIG_FPROBE) += fprobe.o obj-$(CONFIG_RETHOOK) += rethook.o obj-$(CONFIG_FPROBE_EVENTS) += trace_fprobe.o +obj-$(CONFIG_WPROBE_EVENTS) += trace_wprobe.o obj-$(CONFIG_TRACEPOINT_BENCHMARK) += trace_benchmark.o obj-$(CONFIG_RV) += rv/kernel/trace/trace.c +8
-1@@ -5506,8 +5506,12 @@ static const char readme_msg[] =" uprobe_events\t\t- Create/append/remove/show the userspace dynamic events\n" "\t\t\t Write into this file to define/undefine new trace events.\n"#endif +#ifdef CONFIG_WPROBE_EVENTS +" wprobe_events\t\t- Create/append/remove/show the hardware breakpoint dynamic events\n" + "\t\t\t Write into this file to define/undefine new trace events.\n" +#endif #if defined(CONFIG_KPROBE_EVENTS ) || defined(CONFIG_UPROBE_EVENTS ) || \ - defined(CONFIG_FPROBE_EVENTS ) + defined(CONFIG_FPROBE_EVENTS ) || defined(CONFIG_WPROBE_EVENTS ) "\t accepts: event-definitions (one definition per line)\n"#if defined(CONFIG_KPROBE_EVENTS ) || defined(CONFIG_UPROBE_EVENTS )"\t Format: p[:[<group>/][<event>]] <place> [<args>]\n" @@ -5517,6 +5521,9 @@ static const char readme_msg[] ="\t f[:[<group>/][<event>]] <func-name>[%return] [<args>]\n" "\t t[:[<group>/][<event>]] <tracepoint> [<args>]\n"#endif +#ifdef CONFIG_WPROBE_EVENTS + "\t w[:[<group>/][<event>]] [r|w|rw]@<addr>[:<len>]\n" +#endif #ifdef CONFIG_HIST_TRIGGERS "\t s:[synthetic/]<event> <field> [<field>]\n"#endif kernel/trace/trace.h +5
-0@@ -173,6 +173,11 @@ struct fexit_trace_entry_head {unsigned long ret_ip; }; +struct wprobe_trace_entry_head { +struct trace_entry ent; +unsigned long ip; +}; +#define TRACE_BUF_SIZE 1024struct trace_array ;kernel/trace/trace_probe.c +21
-1@@ -968,6 +968,24 @@ static int parse_probe_vars(char *orig_arg, const struct fetch_type *t, goto inval; } +/* wprobe only support "$addr" and "$value" variable */ +if (ctx->flags &TPARG_FL_WPROBE ) { +if (!strcmp (arg,"addr" )) { + code->op =FETCH_OP_BADDR ; +return 0 ; + } +if (!strcmp (arg,"value" )) { + code->op =FETCH_OP_BADDR ; + code++; + code->op =FETCH_OP_DEREF ; + code->offset =0 ; + *pcode = code; +return 0 ; + } + err =TP_ERR_BAD_VAR ; + goto inval; + } +if (str_has_prefix (arg,"retval" )) {if (!(ctx->flags &TPARG_FL_RETURN )) { err =TP_ERR_RETVAL_ON_PROBE ;@@ -1097,8 +1115,9 @@ parse_probe_arg(char *arg, const struct fetch_type *type, ret =parse_probe_vars (arg, type, pcode, end, ctx);break ; +#ifdef CONFIG_HAVE_FUNCTION_ARG_ACCESS_API case '%' :/* named register */ -if (ctx->flags & (TPARG_FL_TEVENT |TPARG_FL_FPROBE )) { +if (ctx->flags & (TPARG_FL_TEVENT |TPARG_FL_FPROBE |TPARG_FL_WPROBE )) {/* eprobe and fprobe do not handle registers */ trace_probe_log_err (ctx->offset,BAD_VAR );break ;@@ -1111,6 +1130,7 @@ parse_probe_arg(char *arg, const struct fetch_type *type, } elsetrace_probe_log_err (ctx->offset,BAD_REG_NAME );break ; +#endif case '@' :/* memory, file-offset or symbol */ if (isdigit (arg[1 ])) {kernel/trace/trace_probe.h +7
-1@@ -89,6 +89,7 @@ enum fetch_op {FETCH_OP_STACK ,/* Stack : .param = index */ FETCH_OP_STACKP ,/* Stack pointer */ FETCH_OP_RETVAL ,/* Return value */ +FETCH_OP_BADDR ,/* Break address */ FETCH_OP_IMM ,/* Immediate : .immediate */ FETCH_OP_COMM ,/* Current comm */ FETCH_OP_ARG, /* Function argument : .param */@@ -396,6 +397,7 @@ static inline int traceprobe_get_entry_data_size(struct trace_probe *tp)#define TPARG_FL_USER BIT(4)#define TPARG_FL_FPROBE BIT(5)#define TPARG_FL_TPOINT BIT(6) +#define TPARG_FL_WPROBE BIT(7)#define TPARG_FL_LOC_MASK GENMASK(4, 0)static inline bool tparg_is_function_entry (unsigned int flags)@@ -556,7 +558,11 @@ extern int traceprobe_define_arg_fields(struct trace_event_call *event_call,C (BAD_TYPE4STR ,"This type does not fit for string." ),\C (NEED_STRING_TYPE ,"$comm and immediate-string only accepts string type" ),\C (TOO_MANY_ARGS ,"Too many arguments are specified" ), \ -C (TOO_MANY_EARGS ,"Too many entry arguments specified" ), +C (TOO_MANY_EARGS ,"Too many entry arguments specified" ), \ +C (BAD_ACCESS_FMT ,"Access memory address requires @" ), \ +C (BAD_ACCESS_TYPE ,"Bad memory access type" ), \ +C (BAD_ACCESS_LEN ,"This memory access length is not supported" ), \ +C (BAD_ACCESS_ADDR ,"Invalid access memory address" ), #undef C #define C(a, b) TP_ERR_##akernel/trace/trace_wprobe.c new file +685
-0@@ -0,0 +1,685 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* Hardware-breakpoint-based tracing events +* +* Copyright (C) 2023, Masami Hiramatsu <[email protected]> +*/ +#define pr_fmt (fmt) "trace_wprobe: " fmt + +#include <linux/hw_breakpoint.h> +#include <linux/kallsyms.h> +#include <linux/list.h> +#include <linux/module.h> +#include <linux/mutex.h> +#include <linux/perf_event.h> +#include <linux/rculist.h> +#include <linux/security.h> +#include <linux/tracepoint.h> +#include <linux/uaccess.h> + +#include <asm/ptrace.h> + +#include "trace_dynevent.h" +#include "trace_probe.h" +#include "trace_probe_kernel.h" +#include "trace_probe_tmpl.h" + +#define WPROBE_EVENT_SYSTEM "wprobes" + +static int trace_wprobe_create (const char *raw_command); +static int trace_wprobe_show (struct seq_file *m,struct dyn_event *ev); +static int trace_wprobe_release (struct dyn_event *ev); +static bool trace_wprobe_is_busy (struct dyn_event *ev); +static bool trace_wprobe_match (const char *system,const char *event, +int argc,const char **argv,struct dyn_event *ev); + +static struct dyn_event_operations trace_wprobe_ops = { + .create = trace_wprobe_create, + .show = trace_wprobe_show, + .is_busy = trace_wprobe_is_busy, + .free = trace_wprobe_release, + .match = trace_wprobe_match, +}; + +struct trace_wprobe { +struct dyn_event devent; +struct perf_event *__percpu *bp_event; +unsigned long addr; +int len; +int type; +const char *symbol; +struct trace_probe tp; +}; + +static bool is_trace_wprobe (struct dyn_event *ev) +{ +return ev->ops == &trace_wprobe_ops; +} + +static struct trace_wprobe *to_trace_wprobe (struct dyn_event *ev) +{ + return container_of(ev, struct trace_wprobe, devent); +} + +#define for_each_trace_wprobe (pos, dpos) \ + for_each_dyn_event(dpos) \ + if (is_trace_wprobe(dpos) && (pos = to_trace_wprobe(dpos))) + +static bool trace_wprobe_is_busy (struct dyn_event *ev) +{ +struct trace_wprobe *tw =to_trace_wprobe (ev); + +return trace_probe_is_enabled (&tw->tp); +} + +static bool trace_wprobe_match (const char *system,const char *event, +int argc,const char **argv,struct dyn_event *ev) +{ +struct trace_wprobe *tw =to_trace_wprobe (ev); + +if (event[0 ] !='\0' &&strcmp (trace_probe_name (&tw->tp), event)) +return false; + +if (system &&strcmp (trace_probe_group_name (&tw->tp), system)) +return false; + +/* TODO: match arguments */ +return true; +} + +/* +* Note that we don't verify the fetch_insn code, since it does not come +* from user space. +*/ +static int +process_fetch_insn (struct fetch_insn *code,void *rec,void *edata, +void *dest,void *base) +{ +void *baddr = rec; +unsigned long val; +int ret; + +retry: +/* 1st stage: get value from context */ +switch (code->op) { +case FETCH_OP_BADDR : + val = (unsigned long )baddr; +break ; +case FETCH_NOP_SYMBOL :/* Ignore a place holder */ + code++; + goto retry; +default : + ret =process_common_fetch_insn (code, &val); +if (ret <0 ) +return ret; + } + code++; + +return process_fetch_insn_bottom (code, val, dest, base); +} +NOKPROBE_SYMBOL (process_fetch_insn) + +static void wprobe_trace_handler(struct trace_wprobe *tw, +struct perf_sample_data *data, +struct pt_regs *regs, +struct trace_event_file *trace_file) +{ +struct wprobe_trace_entry_head *entry; +struct trace_event_call *call =trace_probe_event_call (&tw->tp); +struct trace_event_buffer fbuffer; +int dsize; + +if (WARN_ON_ONCE (call != trace_file->event_call)) +return ; + +if (trace_trigger_soft_disabled (trace_file)) +return ; + + dsize =__get_data_size (&tw->tp, (void *)tw->addr,NULL ); + + entry =trace_event_buffer_reserve (&fbuffer, trace_file, +sizeof (*entry) + tw->tp.size + dsize); +if (!entry) +return ; + + entry->ip =instruction_pointer (regs); +store_trace_args (&entry[1 ], &tw->tp, (void *)tw->addr,NULL ,sizeof (*entry), dsize); + + fbuffer.regs = regs; +trace_event_buffer_commit (&fbuffer); +} + +static void wprobe_perf_handler (struct perf_event *bp, +struct perf_sample_data *data, +struct pt_regs *regs) +{ +struct trace_wprobe *tw = bp->overflow_handler_context; +struct event_file_link *link; + +trace_probe_for_each_link_rcu (link, &tw->tp) +wprobe_trace_handler (tw, data, regs, link->file); +} + +static int __register_trace_wprobe (struct trace_wprobe *tw) +{ +struct perf_event_attr attr; + +if (tw->bp_event) +return -EINVAL ; + +hw_breakpoint_init (&attr); + attr.bp_addr = tw->addr; + attr.bp_len = tw->len; + attr.bp_type = tw->type; + + tw->bp_event =register_wide_hw_breakpoint (&attr, wprobe_perf_handler, tw); +if (IS_ERR ((void *__force )tw->bp_event)) { +int ret =PTR_ERR ((void *__force )tw->bp_event); + + tw->bp_event =NULL ; +return ret; + } + +return 0 ; +} + +static void __unregister_trace_wprobe (struct trace_wprobe *tw) +{ +if (tw->bp_event) { +unregister_wide_hw_breakpoint (tw->bp_event); + tw->bp_event =NULL ; + } +} + +static void free_trace_wprobe (struct trace_wprobe *tw) +{ +if (tw) { +trace_probe_cleanup (&tw->tp); +kfree (tw->symbol); +kfree (tw); + } +} +DEFINE_FREE(free_trace_wprobe, struct trace_wprobe *, if (!IS_ERR_OR_NULL(_T)) free_trace_wprobe(_T)); + +static struct trace_wprobe *alloc_trace_wprobe (const char *group, +const char *event, +const char *symbol, +unsigned long addr, +int len,int type,int nargs) +{ + struct trace_wprobe *tw __free(free_trace_wprobe) = NULL; +int ret; + + tw =kzalloc (struct_size (tw, tp.args, nargs),GFP_KERNEL ); +if (!tw) +return ERR_PTR (-ENOMEM ); + +if (symbol) { + tw->symbol =kstrdup (symbol,GFP_KERNEL ); +if (!tw->symbol) +return ERR_PTR (-ENOMEM ); + } + tw->addr = addr; + tw->len = len; + tw->type = type; + + ret =trace_probe_init (&tw->tp, event, group, false, nargs); +if (ret <0 ) +return ERR_PTR (ret); + +dyn_event_init (&tw->devent, &trace_wprobe_ops); +return_ptr (tw); +} + +static struct trace_wprobe *find_trace_wprobe (const char *event, +const char *group) +{ +struct dyn_event *pos; +struct trace_wprobe *tw; + +for_each_trace_wprobe (tw, pos) +if (strcmp (trace_probe_name (&tw->tp), event) ==0 && +strcmp (trace_probe_group_name (&tw->tp), group) ==0 ) +return tw; +return NULL ; +} + +static enum print_line_t +print_wprobe_event (struct trace_iterator *iter,int flags, +struct trace_event *event) +{ +struct wprobe_trace_entry_head *field; +struct trace_seq *s = &iter->seq; +struct trace_probe *tp; + + field = (struct wprobe_trace_entry_head *)iter->ent; + tp =trace_probe_primary_from_call ( + container_of(event, struct trace_event_call, event)); +if (WARN_ON_ONCE (!tp)) + goto out; + +trace_seq_printf (s,"%s: (" ,trace_probe_name (tp)); + +if (!seq_print_ip_sym (s, field->ip, flags |TRACE_ITER_SYM_OFFSET )) + goto out; + +trace_seq_putc (s,')' ); + +if (trace_probe_print_args (s, tp->args, tp->nr_args, + (u8 *)&field[1 ], field) <0 ) + goto out; + +trace_seq_putc (s,'\n' ); +out: +return trace_handle_return (s); +} + +static int wprobe_event_define_fields (struct trace_event_call *event_call) +{ +int ret; +struct wprobe_trace_entry_head field; +struct trace_probe *tp; + + tp =trace_probe_primary_from_call (event_call); +if (WARN_ON_ONCE (!tp)) +return -ENOENT ; + + DEFINE_FIELD(unsigned long, ip, FIELD_STRING_IP, 0); + +return traceprobe_define_arg_fields (event_call,sizeof (field), tp); +} + +static struct trace_event_functions wprobe_funcs = { + .trace = print_wprobe_event +}; + +static struct trace_event_fields wprobe_fields_array[] = { + { .type =TRACE_FUNCTION_TYPE , + .define_fields = wprobe_event_define_fields }, + {} +}; + +static int wprobe_register (struct trace_event_call *event, +enum trace_reg type,void *data); + +static inline void init_trace_event_call (struct trace_wprobe *tw) +{ +struct trace_event_call *call =trace_probe_event_call (&tw->tp); + + call->event.funcs = &wprobe_funcs; + call->class->fields_array = wprobe_fields_array; + call->flags =TRACE_EVENT_FL_WPROBE ; + call->class->reg = wprobe_register; +} + +static int register_wprobe_event (struct trace_wprobe *tw) +{ +init_trace_event_call (tw); +return trace_probe_register_event_call (&tw->tp); +} + +static int register_trace_wprobe_event (struct trace_wprobe *tw) +{ +struct trace_wprobe *old_tb; +int ret; + +guard (mutex)(&event_mutex); + + old_tb =find_trace_wprobe (trace_probe_name (&tw->tp), +trace_probe_group_name (&tw->tp)); +if (old_tb) +return -EBUSY ; + + ret =register_wprobe_event (tw); +if (ret) +return ret; + +dyn_event_add (&tw->devent,trace_probe_event_call (&tw->tp)); +return 0 ; +} +static int unregister_wprobe_event (struct trace_wprobe *tw) +{ +return trace_probe_unregister_event_call (&tw->tp); +} + +static int unregister_trace_wprobe (struct trace_wprobe *tw) +{ +if (trace_probe_has_sibling (&tw->tp)) + goto unreg; + +if (trace_probe_is_enabled (&tw->tp)) +return -EBUSY ; + +if (trace_event_dyn_busy (trace_probe_event_call (&tw->tp))) +return -EBUSY ; + +if (unregister_wprobe_event (tw)) +return -EBUSY ; + +unreg: +__unregister_trace_wprobe (tw); +dyn_event_remove (&tw->devent); +trace_probe_unlink (&tw->tp); + +return 0 ; +} + +static int enable_trace_wprobe (struct trace_event_call *call, +struct trace_event_file *file) +{ +struct trace_probe *tp; +struct trace_wprobe *tw; +bool enabled; +int ret =0 ; + + tp =trace_probe_primary_from_call (call); +if (WARN_ON_ONCE (!tp)) +return -ENODEV ; + enabled =trace_probe_is_enabled (tp); + +if (file) { + ret =trace_probe_add_file (tp, file); +if (ret) +return ret; + }else { +trace_probe_set_flag (tp,TP_FLAG_PROFILE ); + } + +if (!enabled) { +list_for_each_entry (tw,trace_probe_probe_list (tp), tp.list) { + ret =__register_trace_wprobe (tw); +if (ret <0 ) { +/* TODO: rollback */ +return ret; + } + } + } + +return 0 ; +} + +static int disable_trace_wprobe (struct trace_event_call *call, +struct trace_event_file *file) +{ +struct trace_wprobe *tw; +struct trace_probe *tp; + + tp =trace_probe_primary_from_call (call); +if (WARN_ON_ONCE (!tp)) +return -ENODEV ; + +if (file) { +if (!trace_probe_get_file_link (tp, file)) +return -ENOENT ; +if (!trace_probe_has_single_file (tp)) + goto out; +trace_probe_clear_flag (tp,TP_FLAG_TRACE ); + }else { +trace_probe_clear_flag (tp,TP_FLAG_PROFILE ); + } + +if (!trace_probe_is_enabled (tp)) { +list_for_each_entry (tw,trace_probe_probe_list (tp), tp.list) { +__unregister_trace_wprobe (tw); + } + } + +out: +if (file) +trace_probe_remove_file (tp, file); + +return 0 ; +} + +static int wprobe_register (struct trace_event_call *event, +enum trace_reg type,void *data) +{ +struct trace_event_file *file = data; + +switch (type) { +case TRACE_REG_REGISTER : +return enable_trace_wprobe (event, file); +case TRACE_REG_UNREGISTER : +return disable_trace_wprobe (event, file); + +#ifdef CONFIG_PERF_EVENTS +case TRACE_REG_PERF_REGISTER : +return enable_trace_wprobe (event,NULL ); +case TRACE_REG_PERF_UNREGISTER : +return disable_trace_wprobe (event,NULL ); +case TRACE_REG_PERF_OPEN : +case TRACE_REG_PERF_CLOSE : +case TRACE_REG_PERF_ADD : +case TRACE_REG_PERF_DEL : +return 0 ; +#endif + } +return 0 ; +} + +static int parse_address_spec (const char *spec,unsigned long *addr,int *type, +int *len,char **symbol) +{ + char *_spec __free(kfree) = NULL; +int _len =HW_BREAKPOINT_LEN_4 ; +int _type =HW_BREAKPOINT_RW ; +unsigned long _addr =0 ; +char *at, *col; + + _spec =kstrdup (spec,GFP_KERNEL ); +if (!_spec) +return -ENOMEM ; + + at =strchr (_spec,'@' ); + col =strchr (_spec,':' ); + +if (!at) { +trace_probe_log_err (0 ,BAD_ACCESS_FMT ); +return -EINVAL ; + } + +if (at != _spec) { + *at ='\0' ; + +if (strcmp (_spec,"r" ) ==0 ) + _type =HW_BREAKPOINT_R ; +else if (strcmp (_spec,"w" ) ==0 ) + _type =HW_BREAKPOINT_W ; +else if (strcmp (_spec,"rw" ) ==0 ) + _type =HW_BREAKPOINT_RW ; +else { +trace_probe_log_err (0 ,BAD_ACCESS_TYPE ); +return -EINVAL ; + } + } + +if (col) { + *col ='\0' ; +if (kstrtoint (col +1 ,0 , &_len)) { +trace_probe_log_err (col +1 - _spec,BAD_ACCESS_LEN ); +return -EINVAL ; + } + +switch (_len) { +case 1 : + _len =HW_BREAKPOINT_LEN_1 ; +break ; +case 2 : + _len =HW_BREAKPOINT_LEN_2 ; +break ; +case 4 : + _len =HW_BREAKPOINT_LEN_4 ; +break ; +case 8 : + _len =HW_BREAKPOINT_LEN_8 ; +break ; +default : +trace_probe_log_err (col +1 - _spec,BAD_ACCESS_LEN ); +return -EINVAL ; + } + } + +if (kstrtoul (at +1 ,0 , &_addr) !=0 ) { +char *off_str =strpbrk (at +1 ,"+-" ); +int offset =0 ; + +if (off_str) { +if (kstrtoint (off_str,0 , &offset) !=0 ) { +trace_probe_log_err (off_str - _spec,BAD_PROBE_ADDR ); +return -EINVAL ; + } + *off_str ='\0' ; + } + _addr =kallsyms_lookup_name (at +1 ); +if (!_addr) { +trace_probe_log_err (at +1 - _spec,BAD_ACCESS_ADDR ); +return -ENOENT ; + } + _addr += offset; + *symbol =kstrdup (at +1 ,GFP_KERNEL ); +if (!*symbol) +return -ENOMEM ; + } + + *addr = _addr; + *type = _type; + *len = _len; +return 0 ; +} + +static int __trace_wprobe_create (int argc,const char *argv[]) +{ +/* +* Argument syntax: +* b[:[GRP/][EVENT]] SPEC +* +* SPEC: +* [r|w|rw]@[ADDR|SYMBOL[+OFFS]][:LEN] +*/ + struct traceprobe_parse_context *ctx __free(traceprobe_parse_context) = NULL; + struct trace_wprobe *tw __free(free_trace_wprobe) = NULL; +const char *event =NULL , *group =WPROBE_EVENT_SYSTEM ; + const char *tplog __free(trace_probe_log_clear) = NULL; +char *symbol =NULL ; +unsigned long addr; +int len, type, i; +int ret =0 ; + +if (argv[0 ][0 ] !='w' ) +return -ECANCELED ; + +if (argc <2 ) +return -EINVAL ; + + tplog =trace_probe_log_init ("wprobe" , argc, argv); + +if (argv[0 ][1 ] !='\0' ) { +if (argv[0 ][1 ] !=':' ) { +trace_probe_log_set_index (0 ); +trace_probe_log_err (1 ,BAD_MAXACT_TYPE ); +/* Invalid format */ +return -EINVAL ; + } + event = &argv[0 ][2 ]; + } + +trace_probe_log_set_index (1 ); + ret =parse_address_spec (argv[1 ], &addr, &type, &len, &symbol); +if (ret <0 ) +return ret; + +if (!event) + event = symbol ? symbol :"wprobe" ; + + argc -=2 ; argv +=2 ; + tw =alloc_trace_wprobe (group, event, symbol, addr, len, type, argc); +if (IS_ERR (tw)) +return PTR_ERR (tw); + + ctx =kzalloc (sizeof (*ctx),GFP_KERNEL ); +if (!ctx) +return -ENOMEM ; + + ctx->flags =TPARG_FL_KERNEL |TPARG_FL_WPROBE ; + +/* parse arguments */ +for (i =0 ; i < argc; i++) { +trace_probe_log_set_index (i +2 ); + ctx->offset =0 ; + ret =traceprobe_parse_probe_arg (&tw->tp, i, argv[i], ctx); +if (ret) +return ret;/* This can be -ENOMEM */ + } + + ret =traceprobe_set_print_fmt (&tw->tp,PROBE_PRINT_NORMAL ); +if (ret <0 ) +return ret; + + ret =register_trace_wprobe_event (tw); +if (!ret) + tw =NULL ;/* To avoid free */ + +return ret; +} + +static int trace_wprobe_create (const char *raw_command) +{ +return trace_probe_create (raw_command, __trace_wprobe_create); +} + +static int trace_wprobe_release (struct dyn_event *ev) +{ +struct trace_wprobe *tw =to_trace_wprobe (ev); +int ret =unregister_trace_wprobe (tw); + +if (!ret) +free_trace_wprobe (tw); +return ret; +} + +static int trace_wprobe_show (struct seq_file *m,struct dyn_event *ev) +{ +struct trace_wprobe *tw =to_trace_wprobe (ev); +int i; + +seq_printf (m,"w:%s/%s" ,trace_probe_group_name (&tw->tp), +trace_probe_name (&tw->tp)); + +char type_char; + +if (tw->type ==HW_BREAKPOINT_R ) + type_char ='r' ; +else if (tw->type ==HW_BREAKPOINT_W ) + type_char ='w' ; +else + type_char ='x' ;/* Should be rw */ + +int len; + +if (tw->len ==HW_BREAKPOINT_LEN_1 ) + len =1 ; +else if (tw->len ==HW_BREAKPOINT_LEN_2 ) + len =2 ; +else if (tw->len ==HW_BREAKPOINT_LEN_4 ) + len =4 ; +else + len =8 ; + +if (tw->symbol) +seq_printf (m," %c@%s:%d" , type_char, tw->symbol, len); +else +seq_printf (m," %c@0x%lx:%d" , type_char, tw->addr, len); + +for (i =0 ; i < tw->tp.nr_args; i++) +seq_printf (m," %s=%s" , tw->tp.args[i].name, tw->tp.args[i].comm); +seq_putc (m,'\n' ); + +return 0 ; +} + +static __init int init_wprobe_trace (void ) +{ +return dyn_event_register (&trace_wprobe_ops); +} +fs_initcall (init_wprobe_trace); +
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Masami Hiramatsu (Google)
maintainerPATCH v5 2/8 x86/hw_breakpoint: Unify breakpoint install/uninstall
In reply to Masami Hiramatsu (Google)From: Jinchao Wang <[email protected]>
Consolidate breakpoint management to reduce code duplication. The diffstat was misleading, so the stripped code size is compared instead. After refactoring, it is reduced from 11976 bytes to 11448 bytes on my x86_64 system built with clang.
This also makes it easier to introduce arch_reinstall_hw_breakpoint().
In addition, including linux/types.h to fix a missing build dependency.
--- arch/x86/include/asm/hw_breakpoint.h | 6 + arch/x86/kernel/hw_breakpoint.c | 141 +++++++++++++++++++--------------- 2 files changed, 84 insertions(+), 63 deletions(-)
arch/x86/include/asm/hw_breakpoint.h +6 -0
@@ -5,6 +5,7 @@#include <uapi/asm/hw_breakpoint.h> #define __ARCH_HW_BREAKPOINT_H +#include <linux/types.h> /* * The name should probably be something dealt in
@@ -18,6 +19,11 @@ struct arch_hw_breakpoint {u8 type; }; +enum bp_slot_action { +BP_SLOT_ACTION_INSTALL , +BP_SLOT_ACTION_UNINSTALL , +}; +#include <linux/kdebug.h> #include <linux/percpu.h> #include <linux/list.h>
arch/x86/kernel/hw_breakpoint.c +78 -63
181 lines not on this page · raw message
Masami Hiramatsu (Google)
maintainerPATCH v5 3/8 x86/hw_breakpoint: Add arch_reinstall_hw_breakpoint
In reply to Masami Hiramatsu (Google)From: Jinchao Wang <[email protected]>
The new arch_reinstall_hw_breakpoint() function can be used in an atomic context, unlike the more expensive free and re-allocation path. This allows callers to efficiently re-establish an existing breakpoint.
--- arch/x86/include/asm/hw_breakpoint.h | 2 ++ arch/x86/kernel/hw_breakpoint.c | 9 +++++++++ 2 files changed, 11 insertions(+)
arch/x86/include/asm/hw_breakpoint.h +2 -0
@@ -21,6 +21,7 @@ struct arch_hw_breakpoint {enum bp_slot_action {BP_SLOT_ACTION_INSTALL , +BP_SLOT_ACTION_REINSTALL ,BP_SLOT_ACTION_UNINSTALL , };
@@ -65,6 +66,7 @@ extern int hw_breakpoint_exceptions_notify(struct notifier_block *unused,int arch_install_hw_breakpoint (struct perf_event *bp); +int arch_reinstall_hw_breakpoint (struct perf_event *bp);void arch_uninstall_hw_breakpoint (struct perf_event *bp);void hw_breakpoint_pmu_read (struct perf_event *bp);void hw_breakpoint_pmu_unthrottle (struct perf_event *bp);
arch/x86/kernel/hw_breakpoint.c +9 -0
@@ -99,6 +99,10 @@ static int manage_bp_slot(struct perf_event *bp, enum bp_slot_action action) old_bp =NULL ; new_bp = bp;break ; +case BP_SLOT_ACTION_REINSTALL : + old_bp = bp; + new_bp = bp; +break ;case BP_SLOT_ACTION_UNINSTALL : old_bp = bp; new_bp =NULL ;
@@ -187,6 +191,11 @@ int arch_install_hw_breakpoint(struct perf_event *bp)return arch_manage_bp (bp,BP_SLOT_ACTION_INSTALL ); } +int arch_reinstall_hw_breakpoint (struct perf_event *bp) +{ +return arch_manage_bp (bp,BP_SLOT_ACTION_REINSTALL ); +} +void arch_uninstall_hw_breakpoint (struct perf_event *bp) {arch_manage_bp (bp,BP_SLOT_ACTION_UNINSTALL );
Masami Hiramatsu (Google)
maintainerPATCH v5 4/8 HWBP: Add modify_wide_hw_breakpoint_local() API
In reply to Masami Hiramatsu (Google)From: Masami Hiramatsu (Google) <[email protected]>
Add modify_wide_hw_breakpoint_local() arch-wide interface which allows hwbp users to update watch address on-line. This is available if the arch supports CONFIG_HAVE_REINSTALL_HW_BREAKPOINT.
Note that this allows to change the type only for compatible types, because it does not release and reserve the hwbp slot based on type. For instance, you can not change HW_BREAKPOINT_W to HW_BREAKPOINT_X.
---
Changes in v4:
- Update kerneldoc comment about modify_wide_hw_breakpoint_local according to Randy's comment.
Changes in v2:
- Check type compatibility by checking slot. (Thanks Jinchao!)
--- arch/Kconfig | 10 ++++++++++ arch/x86/Kconfig | 1 + include/linux/hw_breakpoint.h | 6 ++++++ kernel/events/hw_breakpoint.c | 37 +++++++++++++++++++++++++++++++++++++ 4 files changed, 54 insertions(+)
arch/Kconfig +10 -0
@@ -418,6 +418,16 @@ config HAVE_MIXED_BREAKPOINTS_REGS Select this option if your arch implements breakpoints under the latter fashion. +config HAVE_REINSTALL_HW_BREAKPOINT + bool + depends on HAVE_HW_BREAKPOINT + help + Depending on the arch implementation of hardware breakpoints, + some of them are able to update the breakpoint configuration + without release and reserve the hardware breakpoint register. + What configuration is able to update depends on hardware and + software implementation. + config HAVE_USER_RETURN_NOTIFIER bool
arch/x86/Kconfig +1 -0
@@ -247,6 +247,7 @@ config X86 select HAVE_FUNCTION_TRACER select HAVE_GCC_PLUGINS select HAVE_HW_BREAKPOINT + select HAVE_REINSTALL_HW_BREAKPOINT select HAVE_IOREMAP_PROT select HAVE_IRQ_EXIT_ON_IRQ_STACK if X86_64 select HAVE_IRQ_TIME_ACCOUNTING
include/linux/hw_breakpoint.h +6 -0
@@ -81,6 +81,9 @@ register_wide_hw_breakpoint(struct perf_event_attr *attr,perf_overflow_handler_t triggered, void *context); +extern int modify_wide_hw_breakpoint_local (struct perf_event *bp, +struct perf_event_attr *attr); +extern int register_perf_hw_breakpoint (struct perf_event *bp);extern void unregister_hw_breakpoint (struct perf_event *bp);extern void unregister_wide_hw_breakpoint (struct perf_event *__percpu *cpu_events);
@@ -124,6 +127,9 @@ register_wide_hw_breakpoint(struct perf_event_attr *attr,perf_overflow_handler_t triggered, void *context) { return NULL; }static inline int +modify_wide_hw_breakpoint_local (struct perf_event *bp, +struct perf_event_attr *attr) {return -ENOSYS ; } +static inline int register_perf_hw_breakpoint (struct perf_event *bp) {return -ENOSYS ; }static inline void unregister_hw_breakpoint (struct perf_event *bp) { } static inline void
kernel/events/hw_breakpoint.c +37 -0
@@ -887,6 +887,43 @@ void unregister_wide_hw_breakpoint(struct perf_event * __percpu *cpu_events) }EXPORT_SYMBOL_GPL (unregister_wide_hw_breakpoint); +/** +* modify_wide_hw_breakpoint_local - update breakpoint config for local CPU +* @bp: the hwbp perf event for this CPU +* @attr: the new attribute for @bp +* +* This does not release and reserve the slot of a HWBP; it just reuses the +* current slot on local CPU. So the users must update the other CPUs by +* themselves. +* Also, since this does not release/reserve the slot, this can not change the +* type to incompatible type of the HWBP. +* Return err if attr is invalid or the CPU fails to update debug register +* for new @attr. +*/ +#ifdef CONFIG_HAVE_REINSTALL_HW_BREAKPOINT +int modify_wide_hw_breakpoint_local (struct perf_event *bp, +struct perf_event_attr *attr) +{ +int ret; + +if (find_slot_idx (bp->attr.bp_type) !=find_slot_idx (attr->bp_type)) +return -EINVAL ; + + ret =hw_breakpoint_arch_parse (bp, attr,counter_arch_bp (bp)); +if (ret) +return ret; + +return arch_reinstall_hw_breakpoint (bp); +} +#else +int modify_wide_hw_breakpoint_local (struct perf_event *bp, +struct perf_event_attr *attr) +{ +return -EOPNOTSUPP ; +} +#endif +EXPORT_SYMBOL_GPL (modify_wide_hw_breakpoint_local); +/** * hw_breakpoint_is_used - check if breakpoints are currently used *
Masami Hiramatsu (Google)
maintainerPATCH v5 5/8 tracing: wprobe: Add wprobe event trigger
In reply to Masami Hiramatsu (Google)From: Masami Hiramatsu (Google) <[email protected]>
Add wprobe event trigger to set and clear the watch event dynamically. This allows us to set an watchpoint on a given local variables and a slab object instead of static objects.
The trigger syntax is below:
- set_wprobe:WPROBE:FIELD[+OFFSET] [if FILTER]
- clear_wprobe:WPROBE[:FIELD[+OFFSET]] [if FILTER]
set_wprobe sets the address pointed by FIELD[+offset] to the WPROBE event. The FIELD is the field name of trigger event. clear_wprobe clears the watch address of WPROBE event. If the FIELD option is specified, it clears only if the current watch address is same as the given FIELD[+OFFSET] value.
The set_wprobe trigger does not change the type and length, these must be set when creating a new wprobe.
Also, the WPROBE event must be disabled when setting the new trigger and it will be busy afterwards. Recommended usage is to add a new wprobe at NULL address and keep disabled.
---
Changes in v5:
- Following the suggestions, the documentation was revised to suit rst.
Changes in v3:
- Add FIELD option support for clear_wprobe and update document.
- Fix to unregister/free event_trigger_data on file correctly.
- Fix syntax comments.
Changes in v2:
- Getting local cpu perf_event from trace_wprobe directly.
- Remove trace_wprobe_local_perf() because it is conditionally unused.
- Make CONFIG_WPROBE_TRIGGERS a hidden config.
--- Documentation/trace/wprobetrace.rst | 86 +++++++ include/linux/trace_events.h | 1 kernel/trace/Kconfig | 10 + kernel/trace/trace_wprobe.c | 430 +++++++++++++++++++++++++++++++++++ 4 files changed, 527 insertions(+)
Documentation/trace/wprobetrace.rst +86 -0
@@ -67,3 +67,89 @@ Here is an example to add a wprobe event on a variable `jiffies`. <idle>-0 [000] d.Z1. 717.026373: my_jiffies: (tick_do_update_jiffies64+0xbe/0x130) You can see the code which writes to `jiffies` is `tick_do_update_jiffies64()`. + +Combination with trigger action +------------------------------- +The event trigger action can extend the utilization of this wprobe. + +- set_wprobe:WPEVENT:FIELD[+|-ADJUST] +- clear_wprobe:WPEVENT[:FIELD[+|-]ADJUST] + +Set these triggers to the target event, then the WPROBE event will be +setup to trace the memory access at FIELD[+|-ADJUST] address. +When clear_wprobe is hit, if FIELD is NOT specified, the WPEVENT is +forcibly cleared. If FIELD[[+|-]ADJUST] is set, it clears WPEVENT only +if its watching address is the same as the FIELD[[+|-]ADJUST] value. + +Notes: +The set_wprobe trigger does not change the type and length, these +must be set when creating a new wprobe. + +The WPROBE event must be disabled when setting the new trigger +and it will be busy afterwards. Recommended usage is to add a new +wprobe at NULL address and keep disabled. + + +For example, trace the first 8 bytes of the dentry data structure passed +to do_truncate() until it is deleted by __dentry_kill(). +(Note: all tracefs setup uses '>>' so that it does not kick do_truncate()) +:: + + # echo 'w:watch rw@0:8 address=$addr value=+0($addr)' >> dynamic_events + # echo 'f:truncate do_truncate dentry=$arg2' >> dynamic_events + # echo 'set_wprobe:watch:dentry' >> events/fprobes/truncate/trigger + # echo 'f:dentry_kill __dentry_kill dentry=$arg1' >> dynamic_events + # echo 'clear_wprobe:watch:dentry' >> events/fprobes/dentry_kill/trigger + # echo 1 >> events/fprobes/truncate/enable + # echo 1 >> events/fprobes/dentry_kill/enable + + # echo aaa > /tmp/hoge + # echo bbb > /tmp/hoge + # echo ccc > /tmp/hoge + # rm /tmp/hoge + +Then, the trace data will show:: + + # tracer: nop + # + # entries-in-buffer/entries-written: 16/16 #P:8 + # + # _-----=> irqs-off/BH-disabled + # / _----=> need-resched + # | / _---=> hardirq/softirq + # || / _--=> preempt-depth + # ||| / _-=> migrate-disable + # |||| / delay + # TASK-PID CPU# ||||| TIMESTAMP FUNCTION + # | | | ||||| | | + sh-113 [004] ..... 6.467444: truncate: (do_truncate+0x4/0x120) dentry=0xffff8880044f0fd8 + sh-113 [004] ..Zff 6.468534: watch: (lookup_fast+0xaa/0x150) address=0xffff8880044f0fd8 value=0x200080 + sh-113 [004] ..Zff 6.468542: watch: (step_into+0x82/0x360) address=0xffff8880044f0fd8 value=0x200080 + sh-113 [004] ..Zff 6.468547: watch: (step_into+0x9f/0x360) address=0xffff8880044f0fd8 value=0x200080 + sh-113 [004] ..Zff 6.468553: watch: (path_openat+0xb3a/0xe70) address=0xffff8880044f0fd8 value=0x200080 + sh-113 [004] ..Zff 6.468557: watch: (path_openat+0xb9a/0xe70) address=0xffff8880044f0fd8 value=0x200080 + sh-113 [004] ..... 6.468563: truncate: (do_truncate+0x4/0x120) dentry=0xffff8880044f0fd8 + sh-113 [004] ...1. 6.469826: dentry_kill: (__dentry_kill+0x0/0x220) dentry=0xffff8880044f0ea0 + sh-113 [004] ...1. 6.469859: dentry_kill: (__dentry_kill+0x0/0x220) dentry=0xffff8880044f0d68 + rm-118 [001] ..Zff 6.472360: watch: (lookup_fast+0xaa/0x150) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] ..Zff 6.472366: watch: (step_into+0x82/0x360) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] ..Zff 6.472370: watch: (step_into+0x9f/0x360) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] ..Zff 6.472386: watch: (lookup_fast+0xaa/0x150) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] ..Zff 6.472390: watch: (step_into+0x82/0x360) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] ..Zff 6.472394: watch: (step_into+0x9f/0x360) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] ..Zff 6.472415: watch: (lookup_one_qstr_excl+0x2c/0x150) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] ..Zff 6.472419: watch: (lookup_one_qstr_excl+0xd5/0x150) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] ..Zff 6.472424: watch: (may_delete+0x18/0x200) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] ..Zff 6.472428: watch: (may_delete+0x194/0x200) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] ..Zff 6.472446: watch: (vfs_unlink+0x63/0x1c0) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] d.Z.. 6.472528: watch: (dont_mount+0x19/0x30) address=0xffff8880044f0fd8 value=0x200180 + rm-118 [001] ..Zff 6.472533: watch: (vfs_unlink+0x11a/0x1c0) address=0xffff8880044f0fd8 value=0x200180 + rm-118 [001] ..Zff 6.472538: watch: (vfs_unlink+0x12e/0x1c0) address=0xffff8880044f0fd8 value=0x200180 + rm-118 [001] d.Z1. 6.472543: watch: (d_delete+0x61/0xa0) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] d.Z1. 6.472547: watch: (dentry_unlink_inode+0x14/0x110) address=0xffff8880044f0fd8 value=0x200080 + rm-118 [001] d.Z1. 6.472551: watch: (dentry_unlink_inode+0x1e/0x110) address=0xffff8880044f0fd8 value=0x80 + rm-118 [001] d.Z.. 6.472563: watch: (fast_dput+0x8d/0x120) address=0xffff8880044f0fd8 value=0x80 + rm-118 [001] ...1. 6.472567: dentry_kill: (__dentry_kill+0x0/0x220) dentry=0xffff8880044f0fd8 + sh-113 [004] ...2. 6.473049: dentry_kill: (__dentry_kill+0x0/0x220) dentry=0xffff888006e383a8 + +You can see the watch event is correctly configured on the dentry.
include/linux/trace_events.h +1 -0
@@ -720,6 +720,7 @@ enum event_trigger_type {ETT_EVENT_HIST = (1 <<4 ),ETT_HIST_ENABLE = (1 <<5 ),ETT_EVENT_EPROBE = (1 <<6 ), + ETT_EVENT_WPROBE = (1 << 7), };extern int filter_match_preds (struct event_filter *filter,void *rec);
kernel/trace/Kconfig +10 -0
@@ -820,6 +820,16 @@ config WPROBE_EVENTS Those events can be inserted wherever hardware breakpoints can be set, and record accessed memory address and values. +config WPROBE_TRIGGERS + depends on WPROBE_EVENTS + depends on HAVE_REINSTALL_HW_BREAKPOINT + bool + default y + help + This adds an event trigger which will set the wprobe on a specific + field of an event. This allows user to trace the memory access of + an address pointed by the event field. + config BPF_EVENTS depends on BPF_SYSCALL depends on (KPROBE_EVENTS || UPROBE_EVENTS) && PERF_EVENTS
kernel/trace/trace_wprobe.c +430 -0
450 lines not on this page · raw message
Masami Hiramatsu (Google)
maintainerPATCH v5 6/8 selftests: tracing: Add a basic testcase for wprobe
In reply to Masami Hiramatsu (Google)From: Masami Hiramatsu (Google) <[email protected]>
Add 'add_remove_wprobe.tc' testcase for testing wprobe event that tests adding and removing operations of the wprobe event.
---
Changes in v5:
- Enable CONFIG_WPROBE_EVENTS in config for ftrace selftest
--- tools/testing/selftests/ftrace/config | 1 .../ftrace/test.d/dynevent/add_remove_wprobe.tc | 68 ++++++++++++++++++++ 2 files changed, 69 insertions(+) create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/add_remove_wprobe.tc
tools/testing/selftests/ftrace/config +1 -0
@@ -27,3 +27,4 @@ CONFIG_STACK_TRACER=y CONFIG_TRACER_SNAPSHOT=y CONFIG_UPROBES=y CONFIG_UPROBE_EVENTS=y +CONFIG_WPROBE_EVENTS=y
tools/testing/selftests/ftrace/test.d/dynevent/add_remove_wprobe.tc new file +68 -0
68 lines not on this page · raw message
Re: [PATCH v5 6/8] selftests: tracing: Add a basic testcase for wprobe
Quoted 4 lines · Masami Hiramatsu (Google)
From: Masami Hiramatsu (Google) <[email protected]>
Add 'add_remove_wprobe.tc' testcase for testing wprobe event that tests adding and removing operations of the wprobe event.
Since this series has landed in -next we've been seeing hangs on a range of arm64 platforms running the ftrace tests, it looks like it's all of them. Unfortunately the systems lock up with no output as soon as they start trying to do something with wprobes:
# ok 19 Generic dynamic event - add/remove kprobe events # ok 20 Generic dynamic event - add/remove synthetic events # ok 21 Generic dynamic event - add/remove tracepoint probe events # ok 22 Generic dynamic event - add/remove tracepoint probe events on module # ok 23 Generic dynamic event - add/remove/test uprobe events
the next test being add_remove_wprobe.tc, which doesn't seem to complete. Full log (for what little it's worth):
https://lava.sirena.org.uk/scheduler/job/2000440#L1860
I turned on -vvv logging and that generated the rather spectacularly more verbose:
https://lava.sirena.org.uk/scheduler/job/2000676/log_file/plain
(in a somewhat processed format unfortunately.). Looking at that log I do notice a bunch of "unexpected operators" reported by the shell, these systems are running dash not bash, though that doesn't seem related. It looks like the script hangs in reset_trigger_file while grepping the trigger files rather than actually trying to do the test.
Sorry about the delay in reporting this.
Masami Hiramatsu (Google)
maintainerRe: [PATCH v5 6/8] selftests: tracing: Add a basic testcase for wprobe
Quoted 10 lines · On Fri, 24 Oct 2025 22:31:06 +0100 Mark Brown <[email protected]> wrote:
Quoted 4 lines · Masami Hiramatsu (Google)
From: Masami Hiramatsu (Google) <[email protected]>
Add 'add_remove_wprobe.tc' testcase for testing wprobe event that tests adding and removing operations of the wprobe event.
Since this series has landed in -next we've been seeing hangs on a range of arm64 platforms running the ftrace tests, it looks like it's all of them. Unfortunately the systems lock up with no output as soon as they start trying to do something with wprobes:
Oh, thanks for reporting!
Quoted 6 lines
# ok 19 Generic dynamic event - add/remove kprobe events # ok 20 Generic dynamic event - add/remove synthetic events # ok 21 Generic dynamic event - add/remove tracepoint probe events # ok 22 Generic dynamic event - add/remove tracepoint probe events on module # ok 23 Generic dynamic event - add/remove/test uprobe events
OK, let me check.
Quoted 9 lines
the next test being add_remove_wprobe.tc, which doesn't seem to complete. Full log (for what little it's worth):
https://lava.sirena.org.uk/scheduler/job/2000440#L1860I turned on -vvv logging and that generated the rather spectacularly more verbose:
Quoted 7 lines
https://lava.sirena.org.uk/scheduler/job/2000676/log_file/plain(in a somewhat processed format unfortunately.). Looking at that log I do notice a bunch of "unexpected operators" reported by the shell, these systems are running dash not bash, though that doesn't seem related. It looks like the script hangs in
reset_trigger_filewhile grepping the trigger files rather than actually trying to do the test.
Yeah, it seems do nothing on wprobe. Let me check why it happens.
Thanks!
Quoted 2 lines
Sorry about the delay in reporting this.
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Masami Hiramatsu (Google)
maintainerRe: [PATCH v5 6/8] selftests: tracing: Add a basic testcase for wprobe
In reply to Mark BrownQuoted 27 lines · On Fri, 24 Oct 2025 22:31:06 +0100 Mark Brown <[email protected]> wrote:
Quoted 4 lines · Masami Hiramatsu (Google)
From: Masami Hiramatsu (Google) <[email protected]>
Add 'add_remove_wprobe.tc' testcase for testing wprobe event that tests adding and removing operations of the wprobe event.
Since this series has landed in -next we've been seeing hangs on a range of arm64 platforms running the ftrace tests, it looks like it's all of them. Unfortunately the systems lock up with no output as soon as they start trying to do something with wprobes:
# ok 19 Generic dynamic event - add/remove kprobe events # ok 20 Generic dynamic event - add/remove synthetic events # ok 21 Generic dynamic event - add/remove tracepoint probe events # ok 22 Generic dynamic event - add/remove tracepoint probe events on module # ok 23 Generic dynamic event - add/remove/test uprobe eventsthe next test being add_remove_wprobe.tc, which doesn't seem to complete. Full log (for what little it's worth):
https://lava.sirena.org.uk/scheduler/job/2000440#L1860I turned on -vvv logging and that generated the rather spectacularly more verbose:
https://lava.sirena.org.uk/scheduler/job/2000676/log_file/plain
Quoted 7 lines
(in a somewhat processed format unfortunately.). Looking at that log I do notice a bunch of "unexpected operators" reported by the shell, these systems are running dash not bash, though that doesn't seem related. It looks like the script hangs in
reset_trigger_filewhile grepping the trigger files rather than actually trying to do the test.Sorry about the delay in reporting this.
OK, eventually, I confirmed it is stopped on enabling wprobe
+ . /mnt/ftrace/test.d/dynevent/add_remove_wprobe.tc
+ echo 0
+ echo
+ TARGET=jiffies
+ echo 'w:my_wprobe w@jiffies'
+ grep -q my_wprobe dynamic_events
+ '[' 0 -ne 0 ]
+ test -d events/wprobes/my_wprobe
+ '[' 0 -ne 0 ]
+ echo 1
I also confirmed:
~ # cd /sys/kernel/tracing//sys/kernel/tracing # echo 'w:my_wprobe w@jiffies' >> dynamic_events /sys/kernel/tracing # echo 1 > events/wprobes/my_wprobe/enable
Freeze the machine.
Thank you,
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Masami Hiramatsu (Google)
maintainerRe: [PATCH v5 6/8] selftests: tracing: Add a basic testcase for wprobe
Quoted 40 lines · On Mon, 27 Oct 2025 22:43:47 +0900 Masami Hiramatsu (Google)…
Quoted 27 lines · On Fri, 24 Oct 2025 22:31:06 +0100 Mark Brown <[email protected]> wrote:
Quoted 4 lines · Masami Hiramatsu (Google)
From: Masami Hiramatsu (Google) <[email protected]>
Add 'add_remove_wprobe.tc' testcase for testing wprobe event that tests adding and removing operations of the wprobe event.
Since this series has landed in -next we've been seeing hangs on a range of arm64 platforms running the ftrace tests, it looks like it's all of them. Unfortunately the systems lock up with no output as soon as they start trying to do something with wprobes:
# ok 19 Generic dynamic event - add/remove kprobe events # ok 20 Generic dynamic event - add/remove synthetic events # ok 21 Generic dynamic event - add/remove tracepoint probe events # ok 22 Generic dynamic event - add/remove tracepoint probe events on module # ok 23 Generic dynamic event - add/remove/test uprobe eventsthe next test being add_remove_wprobe.tc, which doesn't seem to complete. Full log (for what little it's worth):
https://lava.sirena.org.uk/scheduler/job/2000440#L1860I turned on -vvv logging and that generated the rather spectacularly more verbose:
https://lava.sirena.org.uk/scheduler/job/2000676/log_file/plainQuoted 7 lines
(in a somewhat processed format unfortunately.). Looking at that log I do notice a bunch of "unexpected operators" reported by the shell, these systems are running dash not bash, though that doesn't seem related. It looks like the script hangs in
reset_trigger_filewhile grepping the trigger files rather than actually trying to do the test.Sorry about the delay in reporting this.
OK, eventually, I confirmed it is stopped on enabling wprobe
Quoted 11 lines
+ .
/mnt/ftrace/test.d/dynevent/add_remove_wprobe.tc
+ echo 0
+ echo
+ TARGET=jiffies
+ echo 'w:my_wprobe w@jiffies'
+ grep -qmy_wprobedynamic_events
+ '[' 0 -ne 0 ]
+ test -d events/wprobes/my_wprobe
+ '[' 0 -ne 0 ]
+ echo 1
Interestingly, this stops in the cpu_function_call(). It does not call __perf_install_in_context().
~ # cd /sys/kernel/tracing//sys/kernel/tracing # echo 'w:my_wprobe w@jiffies' >> dynamic_events /sys/kernel/tracing # echo 1 > events/wprobes/my_wprobe/enable
[ 54.942288] trace_wprobe: enable_trace_wprobe called [ 54.945306] trace_wprobe: trying to register wprobes [ 54.947367] trace_wprobe: __register_trace_wprobe called [ 54.949586] trace_wprobe: registering wprobe at addr: 0xffffb6ce429fb200, len: 4, type: 2 [ 54.951639] Creating wide hw breakpoint on CPU 0 [ 54.966390] Creating kernel counter on CPU 0 for event type 5 [ 54.967758] perf_install_in_context: event 00000000736da1d9 ctx 000000005d4db900 cpu 0 [ 54.972015] perf_install_in_context2: event 00000000736da1d9 ctx set to 000000005d4db900 [ 54.976697] cpu_function_call: calling function on CPU 0, func: __perf_install_in_context+0x0/0x2c8
What happen if the cpu calls function on itself by smp_call_function_single() on arm64?
smp_call_function_single(this_cpu, remote_function, &data, 1);
Thank you,
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Masami Hiramatsu (Google)
maintainerRe: [PATCH v5 6/8] selftests: tracing: Add a basic testcase for wprobe
Quoted 13 lines · On Tue, 28 Oct 2025 08:42:22 +0900 Masami Hiramatsu (Google)…
~ # cd
/sys/kernel/tracing//sys/kernel/tracing# echo 'w:my_wprobe w@jiffies' >>dynamic_events/sys/kernel/tracing# echo 1 > events/wprobes/my_wprobe/enable[ 54.942288] trace_wprobe: enable_trace_wprobe called [ 54.945306] trace_wprobe: trying to register wprobes [ 54.947367] trace_wprobe: __register_trace_wprobe called [ 54.949586] trace_wprobe: registering wprobe at addr: 0xffffb6ce429fb200, len: 4, type: 2 [ 54.951639] Creating wide hw breakpoint on CPU 0 [ 54.966390] Creating kernel counter on CPU 0 for event type 5 [ 54.967758] perf_install_in_context: event 00000000736da1d9 ctx 000000005d4db900 cpu 0 [ 54.972015] perf_install_in_context2: event 00000000736da1d9 ctx set to 000000005d4db900 [ 54.976697] cpu_function_call: calling function on CPU 0, func: __perf_install_in_context+0x0/0x2c8
Quoted 4 lines
What happen if the cpu calls function on itself by
smp_call_function_single()on arm64?smp_call_function_single(this_cpu, remote_function, &data, 1);
Sorry, that was printk buffering issue. I used trace_printk() instead and persistent ring buffer[1] to trace it.
[1] https://docs.kernel.org/trace/debugging.html#persistent-buffers-across-boots
~ # echo 1 > /sys/kernel/tracing/instances/boot_map/options/trace_printk_dest ~ # echo 'w:my_wprobe w@jiffies' >> /sys/kernel/tracing/dynamic_events ~ # echo 1 > /sys/kernel/tracing/events/wprobes/my_wprobe/enable QEMU 8.2.2 monitor - type 'help' for more information
(qemu) system_reset
...
~ # cat /sys/kernel/tracing/instances/boot_map/trace # tracer: nop
#
# entries-in-buffer/entries-written: 16/16 #P:1
#
# _-----=> irqs-off/BH-disabled
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / _-=> migrate-disable
# |||| / delay
# TASK-PID CPU# ||||| TIMESTAMP FUNCTION
# | | | ||||| | |
<...>-63 [000] ..... 21.065038: register_wide_hw_breakpoint: Creating wide hw breakpoint on CPU 0
<...>-63 [000] ..... 21.079678: perf_event_create_kernel_counter: Creating kernel counter on CPU 0 for event type 5
<...>-63 [000] ..... 21.080051: perf_install_in_context: perf_install_in_context: event 000000000b3ac4d3 ctx 00000000097d6337 cpu 0
<...>-63 [000] ..... 21.080140: perf_install_in_context: perf_install_in_context2: event 000000000b3ac4d3 ctx set to 00000000097d6337
<...>-63 [000] ..... 21.080939: cpu_function_call: cpu_function_call: calling function on CPU 0, func: __perf_install_in_context+0x0/0x2f0
<...>-63 [000] ..... 21.080966: smp_call_function_single: smp_call_function_single: calling function on CPU 0, func: remote_function+0x0/0x78, wait=1
<...>-63 [000] ...1. 21.080973: smp_call_function_single: smp_call_function_single: running on CPU 0, call CPU 0
<...>-63 [000] ...1. 21.081099: smp_call_function_single: smp_call_function_single: checking for potential deadlock conditions
<...>-63 [000] ...1. 21.081259: generic_exec_single: generic_exec_single: preparing to call function on CPU 0, func: remote_function+0x0/0x78
<...>-63 [000] ...1. 21.081269: generic_exec_single: Executing smp_call_function_single on self CPU 0, func: remote_function+0x0/0x78
<...>-63 [000] d..1. 21.081289: csd_do_func: csd_do_func: CPU 0 executing func remote_function+0x0/0x78
<...>-63 [000] d..1. 21.081429: __perf_install_in_context: __perf_install_in_context: event 000000000b3ac4d3 ctx 00000000097d6337
<...>-63 [000] d..2. 21.083211: hw_breakpoint_control: hw_breakpoint_control: ops=0
<...>-63 [000] d..1. 21.084191: __perf_install_in_context: __perf_install_in_context: event 000000000b3ac4d3 done, ret=0
<...>-63 [000] d..1. 21.084237: csd_do_func: csd_do_func: CPU 0 finished func remote_function+0x0/0x78
<...>-63 [000] d..1. 21.084243: generic_exec_single: Finished csd_lock_record(NULL)~ #
So the last message is right before the local_irq_restore() in generic_exec_single().
static int generic_exec_single(int cpu, call_single_data_t *csd)
{
...
csd_lock_record(csd);
csd_unlock(csd);
local_irq_save(flags);
csd_do_func(func, info, NULL);
csd_lock_record(NULL);
trace_printk("Finished csd_lock_record(NULL)\n"); <-
local_irq_restore(flags);
return 0;Actually, I added another trace_printk() right after generic_exec_single().
err = generic_exec_single(cpu, csd);
trace_printk("generic_exec_single returned %d for CPU %d, func: %pS\n",
err, cpu, func);This means after setting the hw_breakpoint, when enabing the IRQ, the machine is frozen - but qemu is running busy.
Can we specify the kernel memory address to HW breakpoint on arm64?
Thank you,
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Masami Hiramatsu (Google)
maintainerRe: [PATCH v5 6/8] selftests: tracing: Add a basic testcase for wprobe
Quoted 82 lines · On Tue, 28 Oct 2025 10:55:49 +0900 Masami Hiramatsu (Google)…
Quoted 13 lines · On Tue, 28 Oct 2025 08:42:22 +0900 Masami Hiramatsu (Google)…
~ # cd
/sys/kernel/tracing//sys/kernel/tracing# echo 'w:my_wprobe w@jiffies' >>dynamic_events/sys/kernel/tracing# echo 1 > events/wprobes/my_wprobe/enable[ 54.942288] trace_wprobe: enable_trace_wprobe called [ 54.945306] trace_wprobe: trying to register wprobes [ 54.947367] trace_wprobe: __register_trace_wprobe called [ 54.949586] trace_wprobe: registering wprobe at addr: 0xffffb6ce429fb200, len: 4, type: 2 [ 54.951639] Creating wide hw breakpoint on CPU 0 [ 54.966390] Creating kernel counter on CPU 0 for event type 5 [ 54.967758] perf_install_in_context: event 00000000736da1d9 ctx 000000005d4db900 cpu 0 [ 54.972015] perf_install_in_context2: event 00000000736da1d9 ctx set to 000000005d4db900 [ 54.976697] cpu_function_call: calling function on CPU 0, func: __perf_install_in_context+0x0/0x2c8Quoted 4 lines
What happen if the cpu calls function on itself by
smp_call_function_single()on arm64?smp_call_function_single(this_cpu, remote_function, &data, 1);Sorry, that was printk buffering issue. I used
trace_printk()instead and persistent ring buffer[1] to trace it.[1] https://docs.kernel.org/trace/debugging.html#persistent-buffers-across-boots
~ # echo 1 >
/sys/kernel/tracing/instances/boot_map/options/trace_printk_dest~ # echo 'w:my_wprobe w@jiffies' >>/sys/kernel/tracing/dynamic_events~ # echo 1 >/sys/kernel/tracing/events/wprobes/my_wprobe/enableQEMU 8.2.2 monitor - type 'help' for more information
(qemu)system_reset
...~ # cat
/sys/kernel/tracing/instances/boot_map/trace# tracer: nop
#
# entries-in-buffer/entries-written: 16/16 #P:1
#
# _-----=> irqs-off/BH-disabled
# / _----=> need-resched# | / _---=> hardirq/softirq # || / _--=> preempt-depth # ||| / _-=> migrate-disable # |||| / delay # TASK-PID CPU# ||||| TIMESTAMP FUNCTION # | | | ||||| | | <...>-63 [000] ..... 21.065038: register_wide_hw_breakpoint: Creating wide hw breakpoint on CPU 0 <...>-63 [000] ..... 21.079678: perf_event_create_kernel_counter: Creating kernel counter on CPU 0 for event type 5 <...>-63 [000] ..... 21.080051: perf_install_in_context: perf_install_in_context: event 000000000b3ac4d3 ctx 00000000097d6337 cpu 0 <...>-63 [000] ..... 21.080140: perf_install_in_context: perf_install_in_context2: event 000000000b3ac4d3 ctx set to 00000000097d6337 <...>-63 [000] ..... 21.080939: cpu_function_call: cpu_function_call: calling function on CPU 0, func: __perf_install_in_context+0x0/0x2f0 <...>-63 [000] ..... 21.080966: smp_call_function_single: smp_call_function_single: calling function on CPU 0, func: remote_function+0x0/0x78, wait=1 <...>-63 [000] ...1. 21.080973: smp_call_function_single: smp_call_function_single: running on CPU 0, call CPU 0 <...>-63 [000] ...1. 21.081099: smp_call_function_single: smp_call_function_single: checking for potential deadlock conditions <...>-63 [000] ...1. 21.081259: generic_exec_single: generic_exec_single: preparing to call function on CPU 0, func: remote_function+0x0/0x78 <...>-63 [000] ...1. 21.081269: generic_exec_single: Executing smp_call_function_single on self CPU 0, func: remote_function+0x0/0x78 <...>-63 [000] d..1. 21.081289: csd_do_func: csd_do_func: CPU 0 executing func remote_function+0x0/0x78 <...>-63 [000] d..1. 21.081429: __perf_install_in_context: __perf_install_in_context: event 000000000b3ac4d3 ctx 00000000097d6337 <...>-63 [000] d..2. 21.083211: hw_breakpoint_control: hw_breakpoint_control: ops=0 <...>-63 [000] d..1. 21.084191: __perf_install_in_context: __perf_install_in_context: event 000000000b3ac4d3 done, ret=0 <...>-63 [000] d..1. 21.084237: csd_do_func: csd_do_func: CPU 0 finished func remote_function+0x0/0x78 <...>-63 [000] d..1. 21.084243: generic_exec_single: Finished csd_lock_record(NULL)~ #
So the last message is right before the
local_irq_restore()ingeneric_exec_single().static int
generic_exec_single(int cpu, call_single_data_t *csd){ ... csd_lock_record(csd); csd_unlock(csd); local_irq_save(flags); csd_do_func(func, info, NULL); csd_lock_record(NULL); trace_printk("Finished csd_lock_record(NULL)\n"); <- local_irq_restore(flags); return 0;Actually, I added another
trace_printk()right aftergeneric_exec_single().
Quoted 8 lines
err = generic_exec_single(cpu, csd); trace_printk("generic_exec_single returned %d for CPU %d, func: %pS\n", err, cpu, func);This means after setting the
hw_breakpoint, when enabing the IRQ, the machine is frozen - but qemu is running busy.Can we specify the kernel memory address to HW breakpoint on arm64?
Hmm, it seems that jiffies related things are updated frequently and it may cause interrupt storm or infinit recursive call.
Basically, I think it should be temporarily disabled so that the interrupt does not occur during the extension of the HWBP interrupt, but I wonder how this works in arm64?
If you know the path, you may be able to prohibit access to the related variables. But that maybe more difficult than SWBP like kprobes. Maybe this should add at least taint flag.
Thank you,
Quoted 4 lines
Thank you,
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Masami Hiramatsu (Google)
maintainerRe: [PATCH v5 6/8] selftests: tracing: Add a basic testcase for wprobe
Quoted 89 lines · On Wed, 29 Oct 2025 00:42:19 +0900 Masami Hiramatsu (Google)…
Quoted 86 lines · On Tue, 28 Oct 2025 10:55:49 +0900 Masami Hiramatsu (Google)…
Quoted 13 lines · On Tue, 28 Oct 2025 08:42:22 +0900 Masami Hiramatsu (Google)…
~ # cd
/sys/kernel/tracing//sys/kernel/tracing# echo 'w:my_wprobe w@jiffies' >>dynamic_events/sys/kernel/tracing# echo 1 > events/wprobes/my_wprobe/enable[ 54.942288] trace_wprobe: enable_trace_wprobe called [ 54.945306] trace_wprobe: trying to register wprobes [ 54.947367] trace_wprobe: __register_trace_wprobe called [ 54.949586] trace_wprobe: registering wprobe at addr: 0xffffb6ce429fb200, len: 4, type: 2 [ 54.951639] Creating wide hw breakpoint on CPU 0 [ 54.966390] Creating kernel counter on CPU 0 for event type 5 [ 54.967758] perf_install_in_context: event 00000000736da1d9 ctx 000000005d4db900 cpu 0 [ 54.972015] perf_install_in_context2: event 00000000736da1d9 ctx set to 000000005d4db900 [ 54.976697] cpu_function_call: calling function on CPU 0, func: __perf_install_in_context+0x0/0x2c8Quoted 4 lines
What happen if the cpu calls function on itself by
smp_call_function_single()on arm64?smp_call_function_single(this_cpu, remote_function, &data, 1);Sorry, that was printk buffering issue. I used
trace_printk()instead and persistent ring buffer[1] to trace it.[1] https://docs.kernel.org/trace/debugging.html#persistent-buffers-across-boots
~ # echo 1 >
/sys/kernel/tracing/instances/boot_map/options/trace_printk_dest~ # echo 'w:my_wprobe w@jiffies' >>/sys/kernel/tracing/dynamic_events~ # echo 1 >/sys/kernel/tracing/events/wprobes/my_wprobe/enableQEMU 8.2.2 monitor - type 'help' for more information
(qemu)system_reset
...~ # cat
/sys/kernel/tracing/instances/boot_map/trace# tracer: nop
#
# entries-in-buffer/entries-written: 16/16 #P:1
#
# _-----=> irqs-off/BH-disabled
# / _----=> need-resched# | / _---=> hardirq/softirq # || / _--=> preempt-depth # ||| / _-=> migrate-disable # |||| / delay # TASK-PID CPU# ||||| TIMESTAMP FUNCTION # | | | ||||| | | <...>-63 [000] ..... 21.065038: register_wide_hw_breakpoint: Creating wide hw breakpoint on CPU 0 <...>-63 [000] ..... 21.079678: perf_event_create_kernel_counter: Creating kernel counter on CPU 0 for event type 5 <...>-63 [000] ..... 21.080051: perf_install_in_context: perf_install_in_context: event 000000000b3ac4d3 ctx 00000000097d6337 cpu 0 <...>-63 [000] ..... 21.080140: perf_install_in_context: perf_install_in_context2: event 000000000b3ac4d3 ctx set to 00000000097d6337 <...>-63 [000] ..... 21.080939: cpu_function_call: cpu_function_call: calling function on CPU 0, func: __perf_install_in_context+0x0/0x2f0 <...>-63 [000] ..... 21.080966: smp_call_function_single: smp_call_function_single: calling function on CPU 0, func: remote_function+0x0/0x78, wait=1 <...>-63 [000] ...1. 21.080973: smp_call_function_single: smp_call_function_single: running on CPU 0, call CPU 0 <...>-63 [000] ...1. 21.081099: smp_call_function_single: smp_call_function_single: checking for potential deadlock conditions <...>-63 [000] ...1. 21.081259: generic_exec_single: generic_exec_single: preparing to call function on CPU 0, func: remote_function+0x0/0x78 <...>-63 [000] ...1. 21.081269: generic_exec_single: Executing smp_call_function_single on self CPU 0, func: remote_function+0x0/0x78 <...>-63 [000] d..1. 21.081289: csd_do_func: csd_do_func: CPU 0 executing func remote_function+0x0/0x78 <...>-63 [000] d..1. 21.081429: __perf_install_in_context: __perf_install_in_context: event 000000000b3ac4d3 ctx 00000000097d6337 <...>-63 [000] d..2. 21.083211: hw_breakpoint_control: hw_breakpoint_control: ops=0 <...>-63 [000] d..1. 21.084191: __perf_install_in_context: __perf_install_in_context: event 000000000b3ac4d3 done, ret=0 <...>-63 [000] d..1. 21.084237: csd_do_func: csd_do_func: CPU 0 finished func remote_function+0x0/0x78 <...>-63 [000] d..1. 21.084243: generic_exec_single: Finished csd_lock_record(NULL)~ #
So the last message is right before the
local_irq_restore()ingeneric_exec_single().static int
generic_exec_single(int cpu, call_single_data_t *csd){ ... csd_lock_record(csd); csd_unlock(csd); local_irq_save(flags); csd_do_func(func, info, NULL); csd_lock_record(NULL); trace_printk("Finished csd_lock_record(NULL)\n"); <- local_irq_restore(flags); return 0;Actually, I added another
trace_printk()right aftergeneric_exec_single().err = generic_exec_single(cpu, csd); trace_printk("generic_exec_single returned %d for CPU %d, func: %pS\n", err, cpu, func);
Quoted 7 lines
Quoted 4 lines
This means after setting the
hw_breakpoint, when enabing the IRQ, the machine is frozen - but qemu is running busy.Can we specify the kernel memory address to HW breakpoint on arm64?
Hmm, it seems that jiffies related things are updated frequently and it may cause interrupt storm or infinit recursive call.
I added another trace_printk() in el1_watchpt(). It seems el1_watchpt() takes too long and there is no time to do any other things. (Note the interval shown below is only within the el1_watchpt function,
and in reality various processes (save/restore registers etc) for exception handling will be inserted before and after.)
kworker/u32:3-75 [001] d.h2. 43.216706: el1_watchpt: FAR=0xjiffies+0x0/0x40, ESR=0xd6000062, WP index=0, n
est=0
kworker/u32:3-75 [001] d.h2. 43.216750: el1_watchpt: returning to EL1: nest=0 kworker/u32:3-75 [001] d.h2. 43.216816: el1_watchpt: FAR=0xjiffies+0x0/0x40, ESR=0xd6000062, WP index=0, n est=0 kworker/u32:3-75 [001] d.h2. 43.216860: el1_watchpt: returning to EL1: nest=0 kworker/u32:3-75 [001] d.h2. 43.216927: el1_watchpt: FAR=0xjiffies+0x0/0x40, ESR=0xd6000062, WP index=0, n est=0 kworker/u32:3-75 [001] d.h2. 43.216971: el1_watchpt: returning to EL1: nest=0 kworker/u32:3-75 [001] d.h2. 43.217058: el1_watchpt: FAR=0xjiffies+0x0/0x40, ESR=0xd6000062, WP index=0, n est=0 kworker/u32:3-75 [001] d.h2. 43.217106: el1_watchpt: returning to EL1: nest=0 kworker/u32:3-75 [001] d.h2. 43.217175: el1_watchpt: FAR=0xjiffies+0x0/0x40, ESR=0xd6000062, WP index=0, n
est=0
kworker/u32:3-75 [001] d.h2. 43.217219: el1_watchpt: returning to EL1: nest=0
So watching any variables which is frequently updated will almost freeze the system. Hmmm, the handler should check the interval and if it is too frequently, it should disable the wprobe.
Thank you,
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Masami Hiramatsu (Google)
maintainerRe: [PATCH v5 6/8] selftests: tracing: Add a basic testcase for wprobe
Quoted 8 lines · On Wed, 29 Oct 2025 11:43:17 +0900 Masami Hiramatsu (Google)…
Quoted 2 lines
Hmm, it seems that jiffies related things are updated frequently and it may cause interrupt storm or infinit recursive call.
I added another
trace_printk()inel1_watchpt(). It seemsel1_watchpt()takes too long and there is no time to do any other things. (Note the interval shown below is only within theel1_watchptfunction,
and in reality various processes (save/restore registers etc) for exception handling will be inserted before and after.)
Forget about this. I found the root cause. The x86 watchpoint exception happens after the instruction is executed, the arm64 happens before.
Thus what we need is to emulate or do single step the hooked instruction and restart from the next instruction from the watchpoint exception on arm64. I thought hw_breakpoint does that, but doesn't. Should we do this in do_watchpoint() or in user_handler?
Thank you,
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Masami Hiramatsu (Google)
maintainerRe: [PATCH v5 6/8] selftests: tracing: Add a basic testcase for wprobe
Quoted 12 lines · On Wed, 29 Oct 2025 17:20:04 +0900 Masami Hiramatsu (Google)…
Quoted 8 lines · On Wed, 29 Oct 2025 11:43:17 +0900 Masami Hiramatsu (Google)…
Quoted 2 lines
Hmm, it seems that jiffies related things are updated frequently and it may cause interrupt storm or infinit recursive call.
I added another
trace_printk()inel1_watchpt(). It seemsel1_watchpt()takes too long and there is no time to do any other things. (Note the interval shown below is only within theel1_watchptfunction,
and in reality various processes (save/restore registers etc) for exception handling will be inserted before and after.)
Quoted 7 lines
Forget about this. I found the root cause. The x86 watchpoint exception happens after the instruction is executed, the arm64 happens before.
Thus what we need is to emulate or do single step the hooked instruction and restart from the next instruction from the watchpoint exception on arm64. I thought
hw_breakpointdoes that, but doesn't. Should we do this indo_watchpoint()or inuser_handler?
There is a single step execution code but only for default overflow_handlers. This is a bit strange becuase other users can not set it up outside of the arch dependent code. Even if it can, it is simply redundant.
So I made changes below which allow users to set its own custom handler is compatible with perf default overflow handlers.
I confirmed this works on both arm and arm64.
arch/arm64/kernel/hw_breakpoint.c +2 -0
@@ -632,6 +632,7 @@ void do_breakpoint(unsigned long esr, struct pt_regs *regs) addr =instruction_pointer (regs); debug_info = ¤t->thread.debug; +trace_printk ("breakpoint exception at address: 0x%lx\n" , addr);for (i =0 ; i < core_num_brps; ++i) {rcu_read_lock ();
@@ -661,6 +662,7 @@ void do_breakpoint(unsigned long esr, struct pt_regs *regs)rcu_read_unlock (); } +trace_printk ("breakpoint handling complete, step=%d\n" , step);if (!step)return ;
include/linux/perf_event.h +2 -7
@@ -902,6 +902,7 @@ struct perf_event {u64 (*clock)(void);perf_overflow_handler_t overflow_handler;void *overflow_handler_context; +bool default_overflow_compatible;struct bpf_prog *prog;u64 bpf_cookie;
@@ -1505,13 +1506,7 @@ extern int perf_event_output(struct perf_event *event,static inline bool is_default_overflow_handler (struct perf_event *event) { -perf_overflow_handler_t overflow_handler = event->overflow_handler; - -if (likely (overflow_handler == perf_event_output_forward)) -return true; -if (unlikely (overflow_handler == perf_event_output_backward)) -return true; -return false; +return event->default_overflow_compatible; } extern void
kernel/events/core.c +2 -0
@@ -12946,9 +12946,11 @@ perf_event_alloc(struct perf_event_attr *attr, int cpu, }else if (is_write_backward (event)){ event->overflow_handler = perf_event_output_backward; event->overflow_handler_context =NULL ; + event->default_overflow_compatible = true; }else { event->overflow_handler = perf_event_output_forward; event->overflow_handler_context =NULL ; + event->default_overflow_compatible = true; }perf_event__state_init (event);
kernel/trace/trace_wprobe.c +7 -0
@@ -163,6 +163,8 @@ static void wprobe_perf_handler(struct perf_event *bp,static int __register_trace_wprobe (struct trace_wprobe *tw) {struct perf_event_attr attr; +struct perf_event *bp; +int cpu;if (tw->bp_event)return -EINVAL ;
@@ -179,6 +181,11 @@ static int __register_trace_wprobe(struct trace_wprobe *tw) tw->bp_event =NULL ;return ret; } +/* Mark wprobe_perf_handler is compatible with default one. */ +for_each_online_cpu (cpu) { + bp =per_cpu (*tw->bp_event, cpu); + bp->default_overflow_compatible = true; + }return 0 ; }
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Re: [PATCH v5 6/8] selftests: tracing: Add a basic testcase for wprobe
Quoted 9 lines · Masami Hiramatsu
Masami Hiramatsu (Google) <[email protected]> wrote:
There is a single step execution code but only for default
overflow_handlers. This is a bit strange becuase other users can not set it up outside of the arch dependent code. Even if it can, it is simply redundant.So I made changes below which allow users to set its own custom handler is compatible with perf default overflow handlers.
I confirmed this works on both arm and arm64.
I think everyone who knows this code is really snowed under at the minute - can I suggest posting this as a fix for now? This is still broken on arm64, we'll need a fix (or to disable the feature on the affected arches) one way or another for v6.19.
Masami Hiramatsu (Google)
maintainerRe: [PATCH v5 6/8] selftests: tracing: Add a basic testcase for wprobe
Quoted 7 lines · On Wed, 12 Nov 2025 12:15:03 +0000 Mark Brown <[email protected]> wrote:
Quoted 5 lines · Masami Hiramatsu
Masami Hiramatsu (Google) <[email protected]> wrote:
There is a single step execution code but only for default
overflow_handlers. This is a bit strange becuase other users can not set it up outside of the arch dependent code. Even if it can, it is simply redundant.
Quoted 8 lines
Quoted 3 lines
So I made changes below which allow users to set its own custom handler is compatible with perf default overflow handlers.
I confirmed this works on both arm and arm64.I think everyone who knows this code is really snowed under at the minute - can I suggest posting this as a fix for now? This is still broken on arm64, we'll need a fix (or to disable the feature on the affected arches) one way or another for v6.19.
Sorry, let me drop it from for-next soon.
Thanks,
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Masami Hiramatsu (Google)
maintainerPATCH v5 7/8 selftests: tracing: Add syntax testcase for wprobe
In reply to Masami Hiramatsu (Google)From: Masami Hiramatsu (Google) <[email protected]>
Add "wprobe_syntax_errors.tc" testcase for testing syntax errors of the watch probe events.
---
Changes in v3:
- Fix to use "wprobe" prefix for detecting error log.
- Fix an error place with wrong offset.
--- .../test.d/dynevent/wprobes_syntax_errors.tc | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/wprobes_syntax_errors.tc
tools/testing/selftests/ftrace/test.d/dynevent/wprobes_syntax_errors.tc new file +20 -0
@@ -0,0 +1,20 @@ +#!/bin/sh +# SPDX-License-Identifier: GPL-2.0 +# description: Watch probe event parser error log check +# requires: dynamic_events "w[:[<group>/][<event>]] [r|w|rw]@<addr>[:<len>]":README + +check_error() { # command-with-error-pos-by-^ + ftrace_errlog_check 'wprobe' "$1" 'dynamic_events' +} + +check_error 'w ^symbol' # BAD_ACCESS_FMT +check_error 'w ^a@symbol' # BAD_ACCESS_TYPE +check_error 'w w@^symbol' # BAD_ACCESS_ADDR +check_error 'w w@jiffies^+offset' # BAD_ACCESS_ADDR +check_error 'w w@jiffies:^100' # BAD_ACCESS_LEN +check_error 'w w@jiffies ^$arg1' # BAD_VAR +check_error 'w w@jiffies ^$retval' # BAD_VAR +check_error 'w w@jiffies ^$stack' # BAD_VAR +check_error 'w w@jiffies ^%ax' # BAD_VAR + +exit 0
Masami Hiramatsu (Google)
maintainerPATCH v5 8/8 selftests: ftrace: Add wprobe trigger testcase
In reply to Masami Hiramatsu (Google)From: Masami Hiramatsu (Google) <[email protected]>
Add a testcase for checking wprobe trigger. This sets set_wprobe and clear_wprobe triggers on fprobe events to watch dentry access. So this depends on both wprobe and fprobe.
---
Changes in v5:
- Enable CONFIG_WPROBE_TRIGGERS in the config for ftrace test.
Changes in v3:
- Newly added.
--- tools/testing/selftests/ftrace/config | 1 .../ftrace/test.d/trigger/trigger-wprobe.tc | 48 ++++++++++++++++++++ 2 files changed, 49 insertions(+) create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/trigger-wprobe.tc
tools/testing/selftests/ftrace/config +1 -0
@@ -28,3 +28,4 @@ CONFIG_TRACER_SNAPSHOT=y CONFIG_UPROBES=y CONFIG_UPROBE_EVENTS=y CONFIG_WPROBE_EVENTS=y +CONFIG_WPROBE_TRIGGERS=y
tools/testing/selftests/ftrace/test.d/trigger/trigger-wprobe.tc new file +48 -0
49 lines not on this page · raw message