From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Shang XiaoJing <shangxiaojing@huawei.com>, <zanussi@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] tracing: kprobe: Fix potential null-ptr-deref on trace_array in kprobe_event_gen_test_exit()
Date: Thu, 17 Nov 2022 16:14:53 +0900 [thread overview]
Message-ID: <20221117161453.e1dc1c98358017d86a4d5a11@kernel.org> (raw)
In-Reply-To: <20221116215536.120b0b74@gandalf.local.home>
On Wed, 16 Nov 2022 21:55:36 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 8 Nov 2022 23:38:46 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
>
> > > Fixes: 64836248dda2 ("tracing: Add kprobe event command generation test module")
> > > Signed-off-by: Shang XiaoJing <shangxiaojing@huawei.com>
> >
> > This looks good to me.
> >
> > Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Hi Masami,
>
> Did you want me to pull these on top of your probes/urgent branch?
No, I think these patches are already queued on probes/urgent :)
https://kernel.googlesource.com/pub/scm/linux/kernel/git/trace/linux-trace.git/+/210880de4e3945d0ac028894df578063205bef61
>
> I'm going through all my patches now and will be starting the testing
> hopefully later this week.
Thanks!
>
> -- Steve
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2022-11-17 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 1:51 [PATCH v2 0/2] tracing: kprobe: Fix some bug in kprobe_event_gen_test.c Shang XiaoJing
2022-11-08 1:51 ` [PATCH v2 1/2] tracing: kprobe: Fix potential null-ptr-deref on trace_event_file in kprobe_event_gen_test_exit() Shang XiaoJing
2022-11-08 1:51 ` [PATCH v2 2/2] tracing: kprobe: Fix potential null-ptr-deref on trace_array " Shang XiaoJing
2022-11-08 14:38 ` Masami Hiramatsu
2022-11-17 2:55 ` Steven Rostedt
2022-11-17 7:14 ` Masami Hiramatsu [this message]
2022-11-17 16:54 ` Steven Rostedt
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=20221117161453.e1dc1c98358017d86a4d5a11@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=shangxiaojing@huawei.com \
--cc=zanussi@kernel.org \
/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®