[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5EBCF33B-D777-4763-ADC3-0EBE676AC220@fb.com>
Date: Mon, 30 May 2022 05:19:53 +0000
From: Song Liu <songliubraving@...com>
To: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
CC: Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>, Yonghong Song <yhs@...com>,
bpf <bpf@...r.kernel.org>, Kernel Team <Kernel-team@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH] tracing/kprobes: Check whether get_kretprobe() returns
NULL in kretprobe_dispatcher()
> On May 27, 2022, at 8:55 AM, Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:
>
> From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
>
> There is a small chance that get_kretprobe(ri) returns NULL in
> kretprobe_dispatcher() when another CPU unregisters the kretprobe
> right after __kretprobe_trampoline_handler().
>
> To avoid this issue, kretprobe_dispatcher() checks the get_kretprobe()
> return value again. And if it is NULL, it returns soon because that
> kretprobe is under unregistering process.
>
> This issue has been introduced when the kretprobe is decoupled
> from the struct kretprobe_instance by commit d741bf41d7c7
> ("kprobes: Remove kretprobe hash"). Before that commit, the
> struct kretprob_instance::rp directly points the kretprobe
> and it is never be NULL.
>
> Reported-by: Yonghong Song <yhs@...com>
> Fixes: d741bf41d7c7 ("kprobes: Remove kretprobe hash")
> Cc: stable@...r.kernel.org
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@...nel.org>
Acked-by: Song Liu <song@...nel.org>
[...]
Powered by blists - more mailing lists