From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: xkernel.wang@foxmail.com, mingo@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH v2] tracing: check the return value of kstrdup()
Date: Thu, 6 Jan 2022 07:35:54 +0900 [thread overview]
Message-ID: <20220106073554.cc42866d46bd8fe4ed7ecd24@kernel.org> (raw)
In-Reply-To: <20220105171049.5858901b@gandalf.local.home>
On Wed, 5 Jan 2022 17:10:49 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> Masami, can you ack this ?
Yes, this is actual bug. Thanks for fixing!
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Fixes: 33ea4b24277b ("perf/core: Implement the 'perf_uprobe' PMU")
>
> -- Steve
>
>
> On Tue, 14 Dec 2021 09:28:02 +0800
> xkernel.wang@foxmail.com wrote:
>
> > From: Xiaoke Wang <xkernel.wang@foxmail.com>
> >
> > kstrdup() returns NULL when some internal memory errors happen, it is
> > better to check the return value of it so to catch the memory error in
> > time.
> >
> > Signed-off-by: Xiaoke Wang <xkernel.wang@foxmail.com>
> > ---
> > Changelogs:
> > Compare with the last email, this one is using my full name.
> > And I am sorry that I did not notice the bugs in trace_boot.c had been
> > already patched. So I removed the content about trace_boot.c.
> > ---
> > kernel/trace/trace_uprobe.c | 5 +++++
> > 1 files changed, 5 insertions(+)
> >
> > diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c
> > index 225ce56..173ff0f 100644
> > --- a/kernel/trace/trace_uprobe.c
> > +++ b/kernel/trace/trace_uprobe.c
> > @@ -1618,6 +1618,11 @@ create_local_trace_uprobe(char *name, unsigned long offs,
> > tu->path = path;
> > tu->ref_ctr_offset = ref_ctr_offset;
> > tu->filename = kstrdup(name, GFP_KERNEL);
> > + if (!tu->filename) {
> > + ret = -ENOMEM;
> > + goto error;
> > + }
> > +
> > init_trace_event_call(tu);
> >
> > ptype = is_ret_probe(tu) ? PROBE_PRINT_RETURN : PROBE_PRINT_NORMAL;
>
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2022-01-05 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 1:28 [PATCH v2] tracing: check the return value of kstrdup() xkernel.wang
2022-01-05 22:10 ` Steven Rostedt
2022-01-05 22:35 ` Masami Hiramatsu [this message]
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=20220106073554.cc42866d46bd8fe4ed7ecd24@kernel.org \
--to=mhiramat@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=xkernel.wang@foxmail.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;
as well as URLs for NNTP newsgroup(s).