From: Daniel Borkmann <daniel@iogearbox.net>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Yonghong Song <yhs@fb.com>,
bpf <bpf@vger.kernel.org>, Kernel Team <kernel-team@fb.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] tracing/kprobes: Check whether get_kretprobe() returns NULL in kretprobe_dispatcher()
Date: Mon, 30 May 2022 21:33:23 +0200 [thread overview]
Message-ID: <0204f480-cdb0-e49f-9034-602eced02966@iogearbox.net> (raw)
In-Reply-To: <165366693881.797669.16926184644089588731.stgit@devnote2>
On 5/27/22 5:55 PM, Masami Hiramatsu (Google) wrote:
> From: Masami Hiramatsu (Google) <mhiramat@kernel.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@fb.com>
> Fixes: d741bf41d7c7 ("kprobes: Remove kretprobe hash")
> Cc: stable@vger.kernel.org
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Steven, I presume you'll pick this fix up?
Thanks,
Daniel
next prev parent reply other threads:[~2022-05-30 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 15:55 [PATCH] tracing/kprobes: Check whether get_kretprobe() returns NULL in kretprobe_dispatcher() Masami Hiramatsu (Google)
2022-05-30 5:19 ` Song Liu
2022-05-30 19:33 ` Daniel Borkmann [this message]
2022-05-30 22:00 ` Steven Rostedt
2022-06-08 12:38 ` Daniel Borkmann
2022-06-08 13:10 ` Steven Rostedt
2022-06-08 13:57 ` Alexei Starovoitov
2022-06-08 13:59 ` Steven Rostedt
2022-06-17 8:26 ` Daniel Borkmann
2022-06-17 8:32 ` Daniel Borkmann
2022-06-17 16:02 ` Steven Rostedt
2022-06-17 16:09 ` Daniel Borkmann
2022-06-17 17:48 ` Steven Rostedt
2022-06-17 19:59 ` Daniel Borkmann
2022-06-17 10:21 ` Jiri Olsa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0204f480-cdb0-e49f-9034-602eced02966@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox