BUG: demonstration of uprobe/uretprobe corrupted stack traces
Subsystems (3)
Andrii Nakryiko
maintainerPATCH 1/1 BUG: demonstration of uprobe/uretprobe corrupted stack traces
Hi Masami,
We've got reports about partially corrupt stack traces when being captured from uretprobes. Trying the simplest repro seems to confirm that something is not quite right here. I'll try to debug it a bit more this week, but I was hoping for you to take a look as well, if you get a chance.
Simple repro built on top of BPF selftests.
$ sudo ./test_progs -a uprobe_autoattach -v ... FN ADDR 0x55fde0 - 0x55fdef UPROBE SZ 40 (CNT 5) URETPROBE SZ 40 (CNT 5) UPROBE 0x55fde0 URETPROBE 0x55ffd4 UPROBE 0x584653 URETPROBE 0x584653 UPROBE 0x585cc9 URETPROBE 0x585cc9 UPROBE 0x7fa9a31eaca3 URETPROBE 0x7fa9a31eaca3 UPROBE 0x5541f689495641d7 URETPROBE 0x5541f689495641d7 ... #203 uprobe_autoattach:OK Summary: 1/0 PASSED, 0 SKIPPED, 0 FAILED
There seem to be two distinct problems.
1. Last two entries for both uprobe and uretprobe stacks are not user-space addressed (0x7fa9a31eaca3) and the very last one doesn't even look like a valid address (0x5541f689495641d7).
2. Looking at first entry for UPROBE vs URETPROBE, you can see that uprobe one's is correct and points exactly to the beginning of autoattach_trigger_func (0x55fde0) as expected, but uretprobe entry (0x55ffd4) is way out of autoattach_trigger_func (which is just 15 bytes long and ends at 0x55fdef). Using addr2line it shows that it points to:
0x000000000055ffd4: test_uprobe_autoattach at /data/users/andriin/linux/tools/testing/selftests/bpf/prog_tests/uprobe_autoattach.c:33
Which is a valid function and location to which autoattach_trigger_func() should return (see objdump snippet below), but from uretprobe I'd imagine that we are going to get address within traced user function (that is 0x55fde0 - 0x55fdef range), not the return address in a parent function.
55ffc4: 89 83 3c 08 00 00 mov %eax,0x83c(%rbx)
55ffca: 8b 45 e8 mov -0x18(%rbp),%eax
55ffcd: 89 c7 mov %eax,%edi
55ffcf: e8 0c fe ff ff call 55fde0 <autoattach_trigger_func>
--> 55ffd4: 89 45 a8 mov %eax,-0x58(%rbp)
55ffd7: ba ef fd 55 00 mov $0x55fdef,%edxBoth issues above seem unexpected, can you please see if I have some wrong assumptions here?
Thanks in advance for taking a look!
--- tools/testing/selftests/bpf/Makefile | 3 ++- .../selftests/bpf/prog_tests/uprobe_autoattach.c | 14 ++++++++++++++ .../selftests/bpf/progs/test_uprobe_autoattach.c | 11 +++++++++++ 3 files changed, 27 insertions(+), 1 deletion(-)
tools/testing/selftests/bpf/Makefile +2 -1
@@ -23,7 +23,8 @@ BPF_GCC ?= $(shell command -v bpf-gcc;) SAN_CFLAGS ?= CFLAGS += -g -O0 -rdynamic -Wall -Werror $(GENFLAGS) $(SAN_CFLAGS) \ -I$(CURDIR) -I$(INCLUDE_DIR) -I$(GENDIR) -I$(LIBDIR) \ - -I$(TOOLSINCDIR) -I$(APIDIR) -I$(OUTPUT) + -I$(TOOLSINCDIR) -I$(APIDIR) -I$(OUTPUT) -fno-omit-frame-pointer + LDFLAGS += $(SAN_CFLAGS) LDLIBS += -lelf -lz -lrt -lpthread
tools/testing/selftests/bpf/prog_tests/uprobe_autoattach.c +14 -0
@@ -10,6 +10,7 @@ static noinline int autoattach_trigger_func(int arg) asmvolatile ("" );return arg +1 ; } +static noinline int autoattach_trigger_func_post(int arg) { return 0; }void test_uprobe_autoattach (void ) {
@@ -17,6 +18,7 @@ void test_uprobe_autoattach(void)int trigger_val =100 , trigger_ret;size_t malloc_sz =1 ;char *mem; +int i; skel =test_uprobe_autoattach__open_and_load ();if (!ASSERT_OK_PTR (skel,"skel_open" ))
@@ -30,6 +32,18 @@ void test_uprobe_autoattach(void)/* trigger & validate uprobe & uretprobe */ trigger_ret =autoattach_trigger_func (trigger_val); +printf ("FN ADDR %p - %p\n" , autoattach_trigger_func, autoattach_trigger_func_post); +printf ("UPROBE SZ %d (CNT %d) URETPROBE SZ %d (CNT %d)\n" , + skel->bss->uprobe_stack_sz, + skel->bss->uprobe_stack_sz /8 , + skel->bss->uretprobe_stack_sz, + skel->bss->uretprobe_stack_sz /8 ); +for (i =0 ; i < skel->bss->uprobe_stack_sz /8 ; i++) { +printf ("UPROBE %-18p URETPROBE %-18p\n" , + (void *)skel->bss->uprobe_stack[i], + (void *)skel->bss->uretprobe_stack[i]); + } + skel->bss->test_pid =getpid ();/* trigger & validate shared library u[ret]probes attached by name */
tools/testing/selftests/bpf/progs/test_uprobe_autoattach.c +11 -0
@@ -27,11 +27,19 @@ int handle_uprobe_noautoattach(struct pt_regs *ctx)return 0 ; } +__u64 uprobe_stack[128 ]; +__u64 uretprobe_stack[128 ]; +int uprobe_stack_sz, uretprobe_stack_sz; + SEC("uprobe//proc/self/exe:autoattach_trigger_func")int handle_uprobe_byname (struct pt_regs *ctx) { uprobe_byname_parm1 =PT_REGS_PARM1_CORE (ctx); uprobe_byname_ran =1 ; + + uprobe_stack_sz =bpf_get_stack (ctx, + uprobe_stack,sizeof (uprobe_stack), +BPF_F_USER_STACK );return 0 ; }
@@ -40,6 +48,9 @@ int handle_uretprobe_byname(struct pt_regs *ctx) { uretprobe_byname_rc =PT_REGS_RC_CORE (ctx); uretprobe_byname_ran =2 ; + uretprobe_stack_sz =bpf_get_stack (ctx, + uretprobe_stack,sizeof (uretprobe_stack), +BPF_F_USER_STACK );return 0 ; }
Signature · 1 line
2.30.2
Quoted 8 lines · Andrii Nakryiko
Hi Masami,
We've got reports about partially corrupt stack traces when being captured from uretprobes. Trying the simplest repro seems to confirm that something is not quite right here. I'll try to debug it a bit more this week, but I was hoping for you to take a look as well, if you get a chance.
A friendly ping! See below, at this point I'm mostly concerned about #2.
Quoted 15 lines
Simple repro built on top of BPF selftests.
$ sudo ./test_progs -a uprobe_autoattach -v ... FN ADDR 0x55fde0 - 0x55fdef UPROBE SZ 40 (CNT 5) URETPROBE SZ 40 (CNT 5) UPROBE 0x55fde0 URETPROBE 0x55ffd4 UPROBE 0x584653 URETPROBE 0x584653 UPROBE 0x585cc9 URETPROBE 0x585cc9 UPROBE 0x7fa9a31eaca3 URETPROBE 0x7fa9a31eaca3 UPROBE 0x5541f689495641d7 URETPROBE 0x5541f689495641d7 ... #203 uprobe_autoattach:OK Summary: 1/0 PASSED, 0 SKIPPED, 0 FAILED
Quoted 5 lines
There seem to be two distinct problems.
1. Last two entries for both uprobe and uretprobe stacks are not user-space addressed (
0x7fa9a31eaca3) and the very last one doesn't even look like a valid address (0x5541f689495641d7).
We can probably ignore this one, because I suspect it's due to my system-wide libc was built without frame-pointers. So once we got into some API inside libc stack traces got corrupted. But the one below about not getting an address of a probed function for uretprobe still stands. Can you please take a look? Thank you!
Quoted 125 lines
2. Looking at first entry for UPROBE vs URETPROBE, you can see that uprobe one's is correct and points exactly to the beginning of
autoattach_trigger_func(0x55fde0) as expected, but uretprobe entry (0x55ffd4) is way out ofautoattach_trigger_func(which is just 15 bytes long and ends at0x55fdef). Using addr2line it shows that it points to:
0x000000000055ffd4:test_uprobe_autoattachat /data/users/andriin/linux/tools/testing/selftests/bpf/prog_tests/uprobe_autoattach.c:33Which is a valid function and location to which
autoattach_trigger_func()should return (see objdump snippet below), but from uretprobe I'd imagine that we are going to get address within traced user function (that is0x55fde0-0x55fdefrange), not the return address in a parent function.55ffc4: 89 83 3c 08 00 00 mov %eax,0x83c(%rbx) 55ffca: 8b 45 e8 mov -0x18(%rbp),%eax 55ffcd: 89 c7 mov %eax,%edi 55ffcf: e8 0c fe ff ff call 55fde0 <autoattach_trigger_func> --> 55ffd4: 89 45 a8 mov %eax,-0x58(%rbp) 55ffd7: ba ef fd 55 00 mov $0x55fdef,%edxBoth issues above seem unexpected, can you please see if I have some wrong assumptions here?
Thanks in advance for taking a look!
Cc Jiri Olsa <[email protected]>Cc Riham Selim <[email protected]>Signed-off-by Andrii Nakryiko <[email protected]>--- tools/testing/selftests/bpf/Makefile | 3 ++- .../selftests/bpf/prog_tests/uprobe_autoattach.c | 14 ++++++++++++++ .../selftests/bpf/progs/test_uprobe_autoattach.c | 11 +++++++++++ 3 files changed, 27 insertions(+), 1 deletion(-)tools/testing/selftests/bpf/Makefile +2
-1@@ -23,7 +23,8 @@ BPF_GCC ?= $(shell command -v bpf-gcc;) SAN_CFLAGS ?= CFLAGS += -g -O0 -rdynamic -Wall -Werror $(GENFLAGS) $(SAN_CFLAGS) \ -I$(CURDIR) -I$(INCLUDE_DIR) -I$(GENDIR) -I$(LIBDIR) \ - -I$(TOOLSINCDIR) -I$(APIDIR) -I$(OUTPUT) + -I$(TOOLSINCDIR) -I$(APIDIR) -I$(OUTPUT) -fno-omit-frame-pointer + LDFLAGS += $(SAN_CFLAGS) LDLIBS += -lelf -lz -lrt -lpthreadtools/testing/selftests/bpf/prog_tests/uprobe_autoattach.c +14
-0@@ -10,6 +10,7 @@ static noinline int autoattach_trigger_func(int arg) asmvolatile ("" );return arg +1 ; } +static noinline int autoattach_trigger_func_post(int arg) { return 0; }void test_uprobe_autoattach (void ) {@@ -17,6 +18,7 @@ void test_uprobe_autoattach(void)int trigger_val =100 , trigger_ret;size_t malloc_sz =1 ;char *mem; +int i; skel =test_uprobe_autoattach__open_and_load ();if (!ASSERT_OK_PTR (skel,"skel_open" ))@@ -30,6 +32,18 @@ void test_uprobe_autoattach(void)/* trigger & validate uprobe & uretprobe */ trigger_ret =autoattach_trigger_func (trigger_val); +printf ("FN ADDR %p - %p\n" , autoattach_trigger_func, autoattach_trigger_func_post); +printf ("UPROBE SZ %d (CNT %d) URETPROBE SZ %d (CNT %d)\n" , + skel->bss->uprobe_stack_sz, + skel->bss->uprobe_stack_sz /8 , + skel->bss->uretprobe_stack_sz, + skel->bss->uretprobe_stack_sz /8 ); +for (i =0 ; i < skel->bss->uprobe_stack_sz /8 ; i++) { +printf ("UPROBE %-18p URETPROBE %-18p\n" , + (void *)skel->bss->uprobe_stack[i], + (void *)skel->bss->uretprobe_stack[i]); + } + skel->bss->test_pid =getpid ();/* trigger & validate shared library u[ret]probes attached by name */ tools/testing/selftests/bpf/progs/test_uprobe_autoattach.c +11
-1@@ -27,11 +27,19 @@ int handle_uprobe_noautoattach(struct pt_regs *ctx)return 0 ; } +__u64 uprobe_stack[128 ]; +__u64 uretprobe_stack[128 ]; +int uprobe_stack_sz, uretprobe_stack_sz; + SEC("uprobe//proc/self/exe:autoattach_trigger_func")int handle_uprobe_byname (struct pt_regs *ctx) { uprobe_byname_parm1 =PT_REGS_PARM1_CORE (ctx); uprobe_byname_ran =1 ; + + uprobe_stack_sz =bpf_get_stack (ctx, + uprobe_stack,sizeof (uprobe_stack), +BPF_F_USER_STACK );return 0 ; }@@ -40,6 +48,9 @@ int handle_uretprobe_byname(struct pt_regs *ctx) { uretprobe_byname_rc =PT_REGS_RC_CORE (ctx); uretprobe_byname_ran =2 ; + uretprobe_stack_sz =bpf_get_stack (ctx, + uretprobe_stack,sizeof (uretprobe_stack), +BPF_F_USER_STACK );return 0 ; } --2.30.2
Hi Andrii,
Sorry for waiting.
Quoted 6 lines · On Mon, 23 May 2022 22:57:48 -0700 Andrii Nakryiko <[email protected]> wrote:
Hi Masami,
We've got reports about partially corrupt stack traces when being captured from uretprobes. Trying the simplest repro seems to confirm that something is not quite right here. I'll try to debug it a bit more this week, but I was hoping for you to take a look as well, if you get a chance.
Ah, uprobes/uretprobes will be handled by Oleg. But I'll try to explain it as far as I know. Oleg, please correct me if I'm wrong.
Quoted 16 lines
Simple repro built on top of BPF selftests.
$ sudo ./test_progs -a uprobe_autoattach -v ... FN ADDR 0x55fde0 - 0x55fdef UPROBE SZ 40 (CNT 5) URETPROBE SZ 40 (CNT 5) UPROBE 0x55fde0 URETPROBE 0x55ffd4 UPROBE 0x584653 URETPROBE 0x584653 UPROBE 0x585cc9 URETPROBE 0x585cc9 UPROBE 0x7fa9a31eaca3 URETPROBE 0x7fa9a31eaca3 UPROBE 0x5541f689495641d7 URETPROBE 0x5541f689495641d7 ... #203 uprobe_autoattach:OK Summary: 1/0 PASSED, 0 SKIPPED, 0 FAILED
Quoted 5 lines
There seem to be two distinct problems.
1. Last two entries for both uprobe and uretprobe stacks are not user-space addressed (
0x7fa9a31eaca3) and the very last one doesn't even look like a valid address (0x5541f689495641d7).
Hmm, what user-space stack unwinder are you using? I guess it comes from the user-space stack unwinder routine.
Quoted 7 lines
2. Looking at first entry for UPROBE vs URETPROBE, you can see that uprobe one's is correct and points exactly to the beginning of
autoattach_trigger_func(0x55fde0) as expected, but uretprobe entry (0x55ffd4) is way out ofautoattach_trigger_func(which is just 15 bytes long and ends at0x55fdef). Using addr2line it shows that it points to:
Quoted 6 lines
0x000000000055ffd4:test_uprobe_autoattachat /data/users/andriin/linux/tools/testing/selftests/bpf/prog_tests/uprobe_autoattach.c:33Which is a valid function and location to which
autoattach_trigger_func()should return (see objdump snippet below), but from uretprobe I'd imagine that we are going to get address within traced user function (that is0x55fde0-0x55fdefrange), not the return address in a parent function.
No, it is expected behavior. Since the "return probe" probes the function returning, the first entry of the stack address is the address where the function is returned (IOW, the IP address when the probe hit). Not the address of the return instruction. As long as it uses the stack to hook the return of the function, it's impossible in principle.
(if it decodes the function to find the return instruction and replace it with a software breakpoint, it may be possible. But this will not work if the function does tail call etc.)
Quoted 10 lines
55ffc4: 89 83 3c 08 00 00 mov %eax,0x83c(%rbx) 55ffca: 8b 45 e8 mov -0x18(%rbp),%eax 55ffcd: 89 c7 mov %eax,%edi 55ffcf: e8 0c fe ff ff call 55fde0 <autoattach_trigger_func> --> 55ffd4: 89 45 a8 mov %eax,-0x58(%rbp) 55ffd7: ba ef fd 55 00 mov $0x55fdef,%edxBoth issues above seem unexpected, can you please see if I have some wrong assumptions here?
So, #1 maybe we need to look into the stack unwinder (bpf_get_stack()?)
Does this happen if you unwind user-stack from kprobe event? Oleg, would you know anything about this issue?
And #2 is the expected behavior.
Thank you,
Quoted 102 lines
Thanks in advance for taking a look!
Cc Jiri Olsa <[email protected]>Cc Riham Selim <[email protected]>Signed-off-by Andrii Nakryiko <[email protected]>--- tools/testing/selftests/bpf/Makefile | 3 ++- .../selftests/bpf/prog_tests/uprobe_autoattach.c | 14 ++++++++++++++ .../selftests/bpf/progs/test_uprobe_autoattach.c | 11 +++++++++++ 3 files changed, 27 insertions(+), 1 deletion(-)tools/testing/selftests/bpf/Makefile +2
-1@@ -23,7 +23,8 @@ BPF_GCC ?= $(shell command -v bpf-gcc;) SAN_CFLAGS ?= CFLAGS += -g -O0 -rdynamic -Wall -Werror $(GENFLAGS) $(SAN_CFLAGS) \ -I$(CURDIR) -I$(INCLUDE_DIR) -I$(GENDIR) -I$(LIBDIR) \ - -I$(TOOLSINCDIR) -I$(APIDIR) -I$(OUTPUT) + -I$(TOOLSINCDIR) -I$(APIDIR) -I$(OUTPUT) -fno-omit-frame-pointer + LDFLAGS += $(SAN_CFLAGS) LDLIBS += -lelf -lz -lrt -lpthreadtools/testing/selftests/bpf/prog_tests/uprobe_autoattach.c +14
-0@@ -10,6 +10,7 @@ static noinline int autoattach_trigger_func(int arg) asmvolatile ("" );return arg +1 ; } +static noinline int autoattach_trigger_func_post(int arg) { return 0; }void test_uprobe_autoattach (void ) {@@ -17,6 +18,7 @@ void test_uprobe_autoattach(void)int trigger_val =100 , trigger_ret;size_t malloc_sz =1 ;char *mem; +int i; skel =test_uprobe_autoattach__open_and_load ();if (!ASSERT_OK_PTR (skel,"skel_open" ))@@ -30,6 +32,18 @@ void test_uprobe_autoattach(void)/* trigger & validate uprobe & uretprobe */ trigger_ret =autoattach_trigger_func (trigger_val); +printf ("FN ADDR %p - %p\n" , autoattach_trigger_func, autoattach_trigger_func_post); +printf ("UPROBE SZ %d (CNT %d) URETPROBE SZ %d (CNT %d)\n" , + skel->bss->uprobe_stack_sz, + skel->bss->uprobe_stack_sz /8 , + skel->bss->uretprobe_stack_sz, + skel->bss->uretprobe_stack_sz /8 ); +for (i =0 ; i < skel->bss->uprobe_stack_sz /8 ; i++) { +printf ("UPROBE %-18p URETPROBE %-18p\n" , + (void *)skel->bss->uprobe_stack[i], + (void *)skel->bss->uretprobe_stack[i]); + } + skel->bss->test_pid =getpid ();/* trigger & validate shared library u[ret]probes attached by name */ tools/testing/selftests/bpf/progs/test_uprobe_autoattach.c +11
-0@@ -27,11 +27,19 @@ int handle_uprobe_noautoattach(struct pt_regs *ctx)return 0 ; } +__u64 uprobe_stack[128 ]; +__u64 uretprobe_stack[128 ]; +int uprobe_stack_sz, uretprobe_stack_sz; + SEC("uprobe//proc/self/exe:autoattach_trigger_func")int handle_uprobe_byname (struct pt_regs *ctx) { uprobe_byname_parm1 =PT_REGS_PARM1_CORE (ctx); uprobe_byname_ran =1 ; + + uprobe_stack_sz =bpf_get_stack (ctx, + uprobe_stack,sizeof (uprobe_stack), +BPF_F_USER_STACK );return 0 ; }@@ -40,6 +48,9 @@ int handle_uretprobe_byname(struct pt_regs *ctx) { uretprobe_byname_rc =PT_REGS_RC_CORE (ctx); uretprobe_byname_ran =2 ; + uretprobe_stack_sz =bpf_get_stack (ctx, + uretprobe_stack,sizeof (uretprobe_stack), +BPF_F_USER_STACK );return 0 ; }Signature · 1 line
2.30.2
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>
Quoted 74 lines · Masami Hiramatsu
Hi Andrii,
Sorry for waiting.
Quoted 6 lines · On Mon, 23 May 2022 22:57:48 -0700 Andrii Nakryiko <[email protected]> wrote:
Hi Masami,
We've got reports about partially corrupt stack traces when being captured from uretprobes. Trying the simplest repro seems to confirm that something is not quite right here. I'll try to debug it a bit more this week, but I was hoping for you to take a look as well, if you get a chance.
Ah, uprobes/uretprobes will be handled by Oleg. But I'll try to explain it as far as I know. Oleg, please correct me if I'm wrong.
Quoted 16 lines
Simple repro built on top of BPF selftests.
$ sudo ./test_progs -a uprobe_autoattach -v ... FN ADDR 0x55fde0 - 0x55fdef UPROBE SZ 40 (CNT 5) URETPROBE SZ 40 (CNT 5) UPROBE 0x55fde0 URETPROBE 0x55ffd4 UPROBE 0x584653 URETPROBE 0x584653 UPROBE 0x585cc9 URETPROBE 0x585cc9 UPROBE 0x7fa9a31eaca3 URETPROBE 0x7fa9a31eaca3 UPROBE 0x5541f689495641d7 URETPROBE 0x5541f689495641d7 ... #203 uprobe_autoattach:OK Summary: 1/0 PASSED, 0 SKIPPED, 0 FAILEDQuoted 5 lines
There seem to be two distinct problems.
1. Last two entries for both uprobe and uretprobe stacks are not user-space addressed (
0x7fa9a31eaca3) and the very last one doesn't even look like a valid address (0x5541f689495641d7).Hmm, what user-space stack unwinder are you using? I guess it comes from the user-space stack unwinder routine.
Quoted 7 lines
2. Looking at first entry for UPROBE vs URETPROBE, you can see that uprobe one's is correct and points exactly to the beginning of
autoattach_trigger_func(0x55fde0) as expected, but uretprobe entry (0x55ffd4) is way out ofautoattach_trigger_func(which is just 15 bytes long and ends at0x55fdef). Using addr2line it shows that it points to:Quoted 6 lines
0x000000000055ffd4:test_uprobe_autoattachat /data/users/andriin/linux/tools/testing/selftests/bpf/prog_tests/uprobe_autoattach.c:33Which is a valid function and location to which
autoattach_trigger_func()should return (see objdump snippet below), but from uretprobe I'd imagine that we are going to get address within traced user function (that is0x55fde0-0x55fdefrange), not the return address in a parent function.No, it is expected behavior. Since the "return probe" probes the function returning, the first entry of the stack address is the address where the function is returned (IOW, the IP address when the probe hit). Not the address of the return instruction. As long as it uses the stack to hook the return of the function, it's impossible in principle.
(if it decodes the function to find the return instruction and replace it with a software breakpoint, it may be possible. But this will not work if the function does tail call etc.)Quoted 8 lines
55ffc4: 89 83 3c 08 00 00 mov %eax,0x83c(%rbx) 55ffca: 8b 45 e8 mov -0x18(%rbp),%eax 55ffcd: 89 c7 mov %eax,%edi 55ffcf: e8 0c fe ff ff call 55fde0 <autoattach_trigger_func> --> 55ffd4: 89 45 a8 mov %eax,-0x58(%rbp) 55ffd7: ba ef fd 55 00 mov $0x55fdef,%edx
Quoted 7 lines
Quoted 2 lines
Both issues above seem unexpected, can you please see if I have some wrong assumptions here?
So, #1 maybe we need to look into the stack unwinder (
bpf_get_stack()?)
Does this happen if you unwind user-stack from kprobe event? Oleg, would you know anything about this issue?
I suspect that this is due to no-frame-pointer libc, so I haven't dug deeper.
Quoted 2 lines
And #2 is the expected behavior.
Ok, I see, thanks for confirming!
Quoted 14 lines
Thank you,
Quoted 12 lines
Thanks in advance for taking a look!
Cc Jiri Olsa <[email protected]>Cc Riham Selim <[email protected]>Signed-off-by Andrii Nakryiko <[email protected]>--- tools/testing/selftests/bpf/Makefile | 3 ++- .../selftests/bpf/prog_tests/uprobe_autoattach.c | 14 ++++++++++++++ .../selftests/bpf/progs/test_uprobe_autoattach.c | 11 +++++++++++ 3 files changed, 27 insertions(+), 1 deletion(-)
[...]
Quoted 3 lines
--
Masami Hiramatsu (Google) <[email protected]>