From: Daniel Borkmann <daniel@iogearbox.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
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: Fri, 17 Jun 2022 18:09:44 +0200 [thread overview]
Message-ID: <26a91f26-8d9c-e5e4-0a2f-4f17746c28b8@iogearbox.net> (raw)
In-Reply-To: <20220617120254.30bb0f15@gandalf.local.home>
On 6/17/22 6:02 PM, Steven Rostedt wrote:
> On Fri, 17 Jun 2022 10:26:40 +0200
> Daniel Borkmann <daniel@iogearbox.net> wrote:
>
>> Steven, we still have this in our patchwork for tracking so it doesn't fall
>> off the radar. The patch is 3 weeks old by now. Has this been picked up yet,
>> or do you want to Ack and we ship the fix via bpf tree? Just asking as I
>> didn't see any further updates ever since.
>
> Sorry, between traveling for conferences and PTO I fell behind. I'll pull
> this into my urgent queue and start running my tests on it.
Okay, if you pick these fixes up today then I'll toss them from our bpf patchwork.
next prev parent reply other threads:[~2022-06-17 16:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 15:55 Masami Hiramatsu (Google)
2022-05-30 5:19 ` Song Liu
2022-05-30 19:33 ` Daniel Borkmann
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 [this message]
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=26a91f26-8d9c-e5e4-0a2f-4f17746c28b8@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
all inboxes | Powered by JetHome®