2022-05-09 03:18:27

by Tiezhu Yang

Subject: [PATCH v3 0/2] Modify some code about kprobe

v3: no need to change post_kprobe_handler() in patch #2 now,
sorry for the carelessness.

v2:
-- only replace __kprobes with NOKPROBE_SYMBOL() in patch #2
-- update the commit messages

Tiezhu Yang (2):
selftests/ftrace: Save kprobe_events to test log
MIPS: Use NOKPROBE_SYMBOL() instead of __kprobes annotation

arch/mips/kernel/kprobes.c | 36 ++++++++++++++--------
arch/mips/mm/fault.c | 6 ++--
.../ftrace/test.d/kprobe/multiple_kprobes.tc | 2 ++
3 files changed, 30 insertions(+), 14 deletions(-)

--
2.1.0

2022-05-14 01:03:47

by Thomas Bogendoerfer

Subject: Re: [PATCH v3 0/2] Modify some code about kprobe

On Fri, May 06, 2022 at 07:02:01PM +0800, Tiezhu Yang wrote:
> v3: no need to change post_kprobe_handler() in patch #2 now,
> sorry for the carelessness.
>
> v2:
> -- only replace __kprobes with NOKPROBE_SYMBOL() in patch #2
> -- update the commit messages
>
> Tiezhu Yang (2):
> selftests/ftrace: Save kprobe_events to test log
> MIPS: Use NOKPROBE_SYMBOL() instead of __kprobes annotation
>
> arch/mips/kernel/kprobes.c | 36 ++++++++++++++--------
> arch/mips/mm/fault.c | 6 ++--
> .../ftrace/test.d/kprobe/multiple_kprobes.tc | 2 ++
> 3 files changed, 30 insertions(+), 14 deletions(-)
>
> --
> 2.1.0

seires applied to mips-next.

Thomas.

--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]