From: Drew Fustini <drew@beagleboard.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Walleij <linus.walleij@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Jason Kridner <jkridner@beagleboard.org>,
Robert Nelson <robertcnelson@beagleboard.org>,
Joe Perches <joe@perches.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v4 2/2] pinctrl: pinmux: Add pinmux-select debugfs file
Date: Thu, 11 Feb 2021 19:39:18 -0800 [thread overview]
Message-ID: <20210212033918.GC347396@x1> (raw)
In-Reply-To: <CAHp75VeBbv8YzsnOsdXKOwPFd2WpjueCwMgm9mQPR2Xq4zW3QQ@mail.gmail.com>
On Thu, Feb 11, 2021 at 11:53:24AM +0200, Andy Shevchenko wrote:
> On Thu, Feb 11, 2021 at 10:09 AM Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > On Wed, Feb 10, 2021 at 11:33 PM Drew Fustini <drew@beagleboard.org> wrote:
>
>
> > > +#define PINMUX_MAX_NAME 64
>
> > > + if (len > (PINMUX_MAX_NAME * 2)) {
> > > + dev_err(pctldev->dev, "write too big for buffer");
> > > + return -EINVAL;
> > > + }
> > > +
> > > + buf = kzalloc(PINMUX_MAX_NAME * 2, GFP_KERNEL);
>
> > > + ret = strncpy_from_user(buf, user_buf, PINMUX_MAX_NAME * 2);
> >
> > While this guarantees buf is not overflowed...
> >
> > > + if (ret < 0) {
> > > + dev_err(pctldev->dev, "failed to copy buffer from userspace");
> > > + goto free_gname;
> > > + }
> > > + buf[len-1] = '\0';
> > > +
> > > + ret = sscanf(buf, "%s %s", fname, gname);
> >
> > ... one of the two strings can still be longer than PINMUX_MAX_NAME,
> > thus overflowing fname or gname.
> >
> > As buf is already a copy, it may be easier to just find the strings in
> > buf, write the NUL terminators into buf, and set up fname and gname
> > to point to the strings inside buf.
>
> You beat me up to it. I was about to comment the same.
>
> So, indeed, instead of sscanf it's simply better and faster to do just
> something like
>
> fname = strstrip(buf) ;
> if (*fname == '\0') {
> ...
> return -EINVAL;
> }
>
> gname = strchr(fname, ' ');
> if (!gname) {
> ...
> return -EINVAL;
> }
> *gname++ = '\0';
>
> on top of the buf pointer.
>
Thank you for the suggestion about how to implement this. I'll use that
in the next revision.
-Drew
next prev parent reply other threads:[~2021-02-12 3:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 22:28 [PATCH v4 0/2] pinctrl: pinmux: Add pinmux-select debugfs file Drew Fustini
2021-02-10 22:28 ` [PATCH v4 1/2] pinctrl: use to octal permissions for debugfs files Drew Fustini
2021-02-11 7:36 ` Joe Perches
2021-02-11 7:52 ` Drew Fustini
2021-02-10 22:28 ` [PATCH v4 2/2] pinctrl: pinmux: Add pinmux-select debugfs file Drew Fustini
2021-02-11 7:11 ` Dan Carpenter
2021-02-11 7:24 ` Joe Perches
2021-02-11 7:39 ` Dan Carpenter
2021-02-12 3:35 ` Drew Fustini
2021-02-17 8:18 ` Dan Carpenter
2021-02-11 8:09 ` Geert Uytterhoeven
2021-02-11 9:53 ` Andy Shevchenko
2021-02-12 3:39 ` Drew Fustini [this message]
2021-02-12 3:37 ` Drew Fustini
2021-02-11 12:00 ` Dan Carpenter
2021-02-12 3:41 ` Drew Fustini
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=20210212033918.GC347396@x1 \
--to=drew@beagleboard.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andy.shevchenko@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=geert@linux-m68k.org \
--cc=jkridner@beagleboard.org \
--cc=joe@perches.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robertcnelson@beagleboard.org \
--cc=tony@atomide.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).