From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, vsementsov@virtuozzo.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH] cutils: Assert in-range base for string-to-integer conversions
Date: Fri, 7 Dec 2018 11:12:58 +0100 [thread overview]
Message-ID: <9022c85e-9bbd-3500-edcd-c4ff014c5604@redhat.com> (raw)
In-Reply-To: <20181206151856.77503-1-eblake@redhat.com>
On 12/6/18 4:18 PM, Eric Blake wrote:
> POSIX states that the value of endptr is unspecified if strtol()
> fails with EINVAL due to an invalid base argument. Since none of
> the callers to check_strtox_error() initialized endptr, we could
> end up propagating uninitialized data back to a caller on error.
> However, passing an out-of-range base is already a sign of poor
> programming, so let's just assert that base is in range, at which
> point check_strtox_error() can be tightened to assert that it is
> receiving an initialized ep that points somewhere within the
> caller's original string, regardless of whether strto*() succeeded
> or failed with ERANGE.
>
> Reported-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>
> Also tested that this does not negatively impact David's pending
> additions of qemu_strtod{,_finite}(). Thus:
> Based-on: <20181121164421.20780-1-david@redhat.com>
>
> util/cutils.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/util/cutils.c b/util/cutils.c
> index 91930d1bbeb..e098debdc0c 100644
> --- a/util/cutils.c
> +++ b/util/cutils.c
> @@ -278,6 +278,7 @@ int qemu_strtosz_metric(const char *nptr, const char **end, uint64_t *result)
> static int check_strtox_error(const char *nptr, char *ep,
> const char **endptr, int libc_errno)
> {
> + assert(ep >= nptr);
> if (endptr) {
> *endptr = ep;
> }
> @@ -325,6 +326,7 @@ int qemu_strtoi(const char *nptr, const char **endptr, int base,
> char *ep;
> long long lresult;
>
> + assert((unsigned) base <= 36 && base != 1);
> if (!nptr) {
> if (endptr) {
> *endptr = nptr;
> @@ -377,6 +379,7 @@ int qemu_strtoui(const char *nptr, const char **endptr, int base,
> char *ep;
> long long lresult;
>
> + assert((unsigned) base <= 36 && base != 1);
> if (!nptr) {
> if (endptr) {
> *endptr = nptr;
> @@ -433,6 +436,7 @@ int qemu_strtol(const char *nptr, const char **endptr, int base,
> {
> char *ep;
>
> + assert((unsigned) base <= 36 && base != 1);
> if (!nptr) {
> if (endptr) {
> *endptr = nptr;
> @@ -475,6 +479,7 @@ int qemu_strtoul(const char *nptr, const char **endptr, int base,
> {
> char *ep;
>
> + assert((unsigned) base <= 36 && base != 1);
> if (!nptr) {
> if (endptr) {
> *endptr = nptr;
> @@ -502,6 +507,7 @@ int qemu_strtoi64(const char *nptr, const char **endptr, int base,
> {
> char *ep;
>
> + assert((unsigned) base <= 36 && base != 1);
> if (!nptr) {
> if (endptr) {
> *endptr = nptr;
> @@ -525,6 +531,7 @@ int qemu_strtou64(const char *nptr, const char **endptr, int base,
> {
> char *ep;
>
> + assert((unsigned) base <= 36 && base != 1);
> if (!nptr) {
> if (endptr) {
> *endptr = nptr;
> @@ -657,6 +664,7 @@ int parse_uint(const char *s, unsigned long long *value, char **endptr,
> char *endp = (char *)s;
> unsigned long long val = 0;
>
> + assert((unsigned) base <= 36 && base != 1);
> if (!s) {
> r = -EINVAL;
> goto out;
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2018-12-07 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 15:18 [Qemu-devel] [PATCH] cutils: Assert in-range base for string-to-integer conversions Eric Blake
2018-12-06 16:40 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
2018-12-06 16:42 ` Laurent Vivier
2018-12-07 9:59 ` [Qemu-devel] " Markus Armbruster
2018-12-07 10:12 ` Philippe Mathieu-Daudé [this message]
2018-12-07 11:18 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
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=9022c85e-9bbd-3500-edcd-c4ff014c5604@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=vsementsov@virtuozzo.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).