From: Petr Mladek <pmladek@suse.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.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 1/2] kernel.h: Update comment about simple_strto<foo>() functions
Date: Mon, 8 Jul 2019 15:01:59 +0200 [thread overview]
Message-ID: <20190708130159.whefdhz4d65exdns@pathway.suse.cz> (raw)
In-Reply-To: <20190704115532.15679-1-andriy.shevchenko@linux.intel.com>
On Thu 2019-07-04 14:55:31, Andy Shevchenko wrote:
> There were discussions in the past about use cases for
> simple_strto<foo>() functions and, in some rare cases,
> they have a benefit over kstrto<foo>() ones.
>
> Update a comment to reduce confusion about special use cases.
>
> Suggested-by: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> - update comment based on Geert's input
> include/linux/kernel.h | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/kernel.h b/include/linux/kernel.h
> index 0c9bc231107f..63663c44933d 100644
> --- a/include/linux/kernel.h
> +++ b/include/linux/kernel.h
> @@ -332,8 +332,7 @@ int __must_check kstrtoll(const char *s, unsigned int base, long long *res);
> * @res: Where to write the result of the conversion on success.
> *
> * Returns 0 on success, -ERANGE on overflow and -EINVAL on parsing error.
> - * Used as a replacement for the obsolete simple_strtoull. Return code must
> - * be checked.
> + * Used as a replacement for the simple_strtoull. Return code must be checked.
> */
> static inline int __must_check kstrtoul(const char *s, unsigned int base, unsigned long *res)
> {
> @@ -361,8 +360,7 @@ static inline int __must_check kstrtoul(const char *s, unsigned int base, unsign
> * @res: Where to write the result of the conversion on success.
> *
> * Returns 0 on success, -ERANGE on overflow and -EINVAL on parsing error.
> - * Used as a replacement for the obsolete simple_strtoull. Return code must
> - * be checked.
> + * Used as a replacement for the simple_strtoull. Return code must be checked.
> */
> static inline int __must_check kstrtol(const char *s, unsigned int base, long *res)
> {
> @@ -438,7 +436,16 @@ static inline int __must_check kstrtos32_from_user(const char __user *s, size_t
> return kstrtoint_from_user(s, count, base, res);
> }
>
> -/* Obsolete, do not use. Use kstrto<foo> instead */
> +/*
> + * Use kstrto<foo> instead.
> + *
> + * NOTE: The simple_strto<foo> does not check for overflow and,
> + * depending on the input, may give interesting results.
I am a bit confused whether the interesting results are caused
by the buffer overflow or if there is another reason.
If it is because of the overflow, I would remove the 2nd line. I guess
that anyone knows what a buffer overflow might cause.
Otherwise the patch looks fine to me.
Best Regards,
Petr
next prev parent reply other threads:[~2019-07-08 13:02 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
2019-07-08 13:42 ` David Laight
2019-07-08 13:56 ` Petr Mladek
2019-07-08 13:01 ` Petr Mladek [this message]
2019-07-08 13:13 ` [PATCH v3 1/2] kernel.h: Update comment about simple_strto<foo>() functions 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=20190708130159.whefdhz4d65exdns@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.com \
--cc=miguel.ojeda.sandonis@gmail.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