mirror of https://github.com/torvalds/linux.git
777f290ab3
In 'NOFENTRY_ARGS' test case for syntax check, any offset X of
`vfs_read+X` except function entry offset (0) fits the criterion,
even if that offset is not at instruction boundary, as the parser
comes before probing. But with "ENDBR64" instruction on x86, offset
4 is treated as function entry. So, X can't be 4 as well. Thus, 8
was used as offset for the test case. On 64-bit powerpc though, any
offset <= 16 can be considered function entry depending on build
configuration (see arch_kprobe_on_func_entry() for implementation
details). So, use `vfs_read+20` to accommodate that scenario too.
Link: https://lore.kernel.org/r/20241129202621.721159-1-hbathini@linux.ibm.com
Fixes:
|
||
|---|---|---|
| .. | ||
| add_and_remove.tc | ||
| busy_check.tc | ||
| kprobe_args.tc | ||
| kprobe_args_char.tc | ||
| kprobe_args_comm.tc | ||
| kprobe_args_string.tc | ||
| kprobe_args_symbol.tc | ||
| kprobe_args_syntax.tc | ||
| kprobe_args_type.tc | ||
| kprobe_args_user.tc | ||
| kprobe_args_vfs.tc | ||
| kprobe_eventname.tc | ||
| kprobe_ftrace.tc | ||
| kprobe_insn_boundary.tc | ||
| kprobe_module.tc | ||
| kprobe_multiprobe.tc | ||
| kprobe_non_uniq_symbol.tc | ||
| kprobe_opt_types.tc | ||
| kprobe_syntax_errors.tc | ||
| kretprobe_args.tc | ||
| kretprobe_entry_arg.tc | ||
| kretprobe_maxactive.tc | ||
| kretprobe_return_suffix.tc | ||
| multiple_kprobes.tc | ||
| probepoint.tc | ||
| profile.tc | ||
| uprobe_syntax_errors.tc | ||