From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Miguel Ojeda Sandonis <miguel.ojeda.sandonis@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mans Rullgard <mans@mansr.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] auxdisplay: charlcd: Deduplicate simple_strtoul()
Date: Mon, 8 Jul 2019 16:35:34 +0300 [thread overview]
Message-ID: <20190708133534.GO9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190708131652.s3gdoieixgyekued@pathway.suse.cz>
On Mon, Jul 08, 2019 at 03:16:52PM +0200, Petr Mladek wrote:
> On Thu 2019-07-04 14:55:32, Andy Shevchenko wrote:
> > Like in the commit
> > 8b2303de399f ("serial: core: Fix handling of options after MMIO address")
> > we may use simple_strtoul() which in comparison to kstrtoul() can do conversion
> > in-place without additional and unnecessary code to be written.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> > - no change since v2
> > drivers/auxdisplay/charlcd.c | 34 +++++++---------------------------
> > 1 file changed, 7 insertions(+), 27 deletions(-)
> >
> > diff --git a/drivers/auxdisplay/charlcd.c b/drivers/auxdisplay/charlcd.c
> > index 92745efefb54..3858dc7a4154 100644
> > --- a/drivers/auxdisplay/charlcd.c
> > +++ b/drivers/auxdisplay/charlcd.c
> > @@ -287,31 +287,6 @@ static int charlcd_init_display(struct charlcd *lcd)
> > return 0;
> > }
> >
> > -/*
> > - * Parses an unsigned integer from a string, until a non-digit character
> > - * is found. The empty string is not accepted. No overflow checks are done.
> > - *
> > - * Returns whether the parsing was successful. Only in that case
> > - * the output parameters are written to.
> > - *
> > - * TODO: If the kernel adds an inplace version of kstrtoul(), this function
> > - * could be easily replaced by that.
> > - */
> > -static bool parse_n(const char *s, unsigned long *res, const char **next_s)
> > -{
> > - if (!isdigit(*s))
> > - return false;
> > -
> > - *res = 0;
> > - while (isdigit(*s)) {
> > - *res = *res * 10 + (*s - '0');
> > - ++s;
> > - }
> > -
> > - *next_s = s;
> > - return true;
> > -}
> > -
> > /*
> > * Parses a movement command of the form "(.*);", where the group can be
> > * any number of subcommands of the form "(x|y)[0-9]+".
> > @@ -336,6 +311,7 @@ static bool parse_xy(const char *s, unsigned long *x, unsigned long *y)
> > {
> > unsigned long new_x = *x;
> > unsigned long new_y = *y;
> > + char *p;
> >
> > for (;;) {
> > if (!*s)
> > @@ -345,11 +321,15 @@ static bool parse_xy(const char *s, unsigned long *x, unsigned long *y)
> > break;
> >
> > if (*s == 'x') {
> > - if (!parse_n(s + 1, &new_x, &s))
> > + new_x = simple_strtoul(s + 1, &p, 10);
>
> simple_strtoul() tries to detect the base even when it has been
> explicitely specified.
I can't see it from the code. Can you point out to this drastic bug that has to
be fixed?
> I am afraid that it might cause some
> regressions.
>
> For example, the following input is strange but it is valid:
>
> x0x10; new code would return (16, <orig_y>) instead of (10, <orig_y>)
> x010; new code would return (8, <orig_y>) instead of (10, <orig_y>)
>
> Best Regards,
> Petr
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-07-08 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 11:55 [PATCH v3 1/2] kernel.h: Update comment about simple_strto<foo>() functions Andy Shevchenko
2019-07-04 11:55 ` [PATCH v3 2/2] auxdisplay: charlcd: Deduplicate simple_strtoul() Andy Shevchenko
2019-07-08 13:16 ` Petr Mladek
2019-07-08 13:35 ` Andy Shevchenko [this message]
2019-07-08 13:42 ` David Laight
2019-07-08 13:56 ` Petr Mladek
2019-07-08 13:01 ` [PATCH v3 1/2] kernel.h: Update comment about simple_strto<foo>() functions Petr Mladek
2019-07-08 13:13 ` Geert Uytterhoeven
2019-07-08 13:48 ` Petr Mladek
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=20190708133534.GO9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=pmladek@suse.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