[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210617044124.pv4xm47cum4faaeo@treble>
Date: Wed, 16 Jun 2021 23:41:24 -0500
From: Josh Poimboeuf <jpoimboe@...hat.com>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...nel.org>, X86 ML <x86@...nel.org>,
Daniel Xu <dxu@...uu.xyz>, linux-kernel@...r.kernel.org,
bpf@...r.kernel.org, kuba@...nel.org, mingo@...hat.com,
ast@...nel.org, tglx@...utronix.de, kernel-team@...com, yhs@...com,
linux-ia64@...r.kernel.org,
Abhishek Sagar <sagar.abhishek@...il.com>,
Andrii Nakryiko <andrii.nakryiko@...il.com>
Subject: Re: [PATCH -tip v7 11/13] x86/unwind: Recover kretprobe trampoline
entry
On Thu, May 27, 2021 at 03:40:48PM +0900, Masami Hiramatsu wrote:
> Since the kretprobe replaces the function return address with
> the kretprobe_trampoline on the stack, x86 unwinders can not
> continue the stack unwinding at that point, or record
> kretprobe_trampoline instead of correct return address.
>
> To fix this issue, find the correct return address from task's
> kretprobe_instances as like as function-graph tracer does.
>
> With this fix, the unwinder can correctly unwind the stack
> from kretprobe event on x86, as below.
>
> <...>-135 [003] ...1 6.722338: r_full_proxy_read_0: (vfs_read+0xab/0x1a0 <- full_proxy_read)
> <...>-135 [003] ...1 6.722377: <stack trace>
> => kretprobe_trace_func+0x209/0x2f0
> => kretprobe_dispatcher+0x4a/0x70
> => __kretprobe_trampoline_handler+0xca/0x150
> => trampoline_handler+0x44/0x70
> => kretprobe_trampoline+0x2a/0x50
> => vfs_read+0xab/0x1a0
> => ksys_read+0x5f/0xe0
> => do_syscall_64+0x33/0x40
> => entry_SYSCALL_64_after_hwframe+0x44/0xae
>
>
> Reported-by: Daniel Xu <dxu@...uu.xyz>
> Signed-off-by: Masami Hiramatsu <mhiramat@...nel.org>
> Suggested-by: Josh Poimboeuf <jpoimboe@...hat.com>
> Tested-by: Andrii Nakryik <andrii@...nel.org>
Acked-by: Josh Poimboeuf <jpoimboe@...hat.com>
--
Josh
Powered by blists - more mailing lists