From: Eric Blake <eblake@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4] inet_listen_opts: add error checking
Date: Fri, 13 Dec 2013 05:42:11 -0700 [thread overview]
Message-ID: <52AB00A3.7010901@redhat.com> (raw)
In-Reply-To: <1386929555-3374-1-git-send-email-kraxel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
On 12/13/2013 03:12 AM, Gerd Hoffmann wrote:
> Don't use atoi() function which doesn't detect errors, switch to
> strtol and error out on failures. Also add a range check while
> being at it.
>
> [ v4: didn't commit buildfix. -ENOCOFFEE. sorry for the spam ]
> [ v3: oops, v2 didn't build ]
> [ v2: use parse_uint_full instead of strtol ]
Patch changelog belongs...
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
...here. You can add a '---' separator in your commit message (and thus
have two '---' lines in 'git send-email' output), if you still want to
track the changelog in your commits (but remember to hoist your S-o-B
when doing that).
> util/qemu-sockets.c | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> + if (port_offset) {
> + unsigned long long baseport;
> + if (parse_uint_full(port, &baseport, 10) < 0) {
> + error_setg(errp, "can't convert to a number: %s", port);
> + return -1;
> + }
> + if (baseport + port_offset > 65535) {
> + error_setg(errp, "port %s out of range", port);
error_setg() is still reporting on a bogus errno value at this point.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-12-13 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 10:12 [Qemu-devel] [PATCH v4] inet_listen_opts: add error checking Gerd Hoffmann
2013-12-13 12:42 ` Eric Blake [this message]
2013-12-13 12:49 ` Eric Blake
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=52AB00A3.7010901@redhat.com \
--to=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).