From: Masami Hiramatsu <mhiramat@kernel.org>
To: Jann Horn <jannh@google.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
kernel list <linux-kernel@vger.kernel.org>,
Song Liu <songliubraving@fb.com>
Subject: Re: [PATCH] perf/core: use strndup_user() instead of buggy open-coded version
Date: Thu, 21 Feb 2019 01:00:52 +0900 [thread overview]
Message-ID: <20190221010052.4da503e3c4252d46620c8276@kernel.org> (raw)
In-Reply-To: <CAG48ez20Hipk2VWjXmbWmC+LVqywAcGOF_Wq-ooO-dLh+EadaQ@mail.gmail.com>
Hi Jann,
On Wed, 20 Feb 2019 16:19:10 +0100
Jann Horn <jannh@google.com> wrote:
> On Tue, Feb 19, 2019 at 3:51 PM Masami Hiramatsu <mhiramat@kernel.org> wrote:
> > On Tue, 19 Feb 2019 20:45:02 +0900
> > Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >
> > > On Mon, 18 Feb 2019 23:07:23 +0100
> > > Jann Horn <jannh@google.com> wrote:
> > >
> > > > The first version of this method was missing the check for
> > > > `ret == PATH_MAX`; then such a check was added, but it didn't call kfree()
> > > > on error, so there was still a small memory leak in the error case.
> > > > Fix it by using strndup_user() instead of open-coding it.
> > > >
> > >
> > > This looks good to me.
> > >
> > > Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
> >
> > BTW, I think it should note that if the string is longer than PATH_MAX.
> > caller will receive -EINVAL instead of -E2BIG with this fix.
>
> Oh, whoops, I hadn't noticed that.
>
> Do you want me to just add a note to the changelog, or do I have to
> work around this in the code?
I think work around will be good if this goes to stable, since I guess
this return code may go to user space.
Thank you,
>
> > > > Fixes: 0eadcc7a7bc0 ("perf/core: Fix perf_uprobe_init()")
> > > > Signed-off-by: Jann Horn <jannh@google.com>
> > > > ---
> > > > compile-tested only
> > > >
> > > > kernel/trace/trace_event_perf.c | 14 +++++---------
> > > > 1 file changed, 5 insertions(+), 9 deletions(-)
> > > >
> > > > diff --git a/kernel/trace/trace_event_perf.c b/kernel/trace/trace_event_perf.c
> > > > index 76217bbef815..c744b02081c3 100644
> > > > --- a/kernel/trace/trace_event_perf.c
> > > > +++ b/kernel/trace/trace_event_perf.c
> > > > @@ -299,15 +299,11 @@ int perf_uprobe_init(struct perf_event *p_event,
> > > >
> > > > if (!p_event->attr.uprobe_path)
> > > > return -EINVAL;
> > > > - path = kzalloc(PATH_MAX, GFP_KERNEL);
> > > > - if (!path)
> > > > - return -ENOMEM;
> > > > - ret = strncpy_from_user(
> > > > - path, u64_to_user_ptr(p_event->attr.uprobe_path), PATH_MAX);
> > > > - if (ret == PATH_MAX)
> > > > - return -E2BIG;
> > > > - if (ret < 0)
> > > > - goto out;
> > > > +
> > > > + path = strndup_user(u64_to_user_ptr(p_event->attr.uprobe_path),
> > > > + PATH_MAX);
> > > > + if (IS_ERR(path))
> > > > + return PTR_ERR(path);
> > > > if (path[0] == '\0') {
> > > > ret = -EINVAL;
> > > > goto out;
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2019-02-20 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 22:07 Jann Horn
2019-02-19 11:45 ` Masami Hiramatsu
2019-02-19 14:51 ` Masami Hiramatsu
2019-02-20 15:19 ` Jann Horn
2019-02-20 16:00 ` 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=20190221010052.4da503e3c4252d46620c8276@kernel.org \
--to=mhiramat@kernel.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@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
Powered by JetHome