qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] pci: rewrite devaddr parsing
Date: Thu, 16 Feb 2012 13:39:02 -0700	[thread overview]
Message-ID: <4F3D6966.8090401@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1202162323260.2192@linmac>

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

On 02/16/2012 12:23 PM, malc wrote:
> On Thu, 16 Feb 2012, Michael S. Tsirkin wrote:
> 
>> Use scanf instead of manual string scanning.
>>
>> +
>> +    /* Parse [[<domain>:]<bus>:]<slot> */
>> +    sscanf(addr, "%x:%x:%x%n", &dom, &bus, &slot, &n);
> 
> sscanf can fail.

Worse, the *scanf family has undefined behavior on integer overflow.  If
addr contains "100000000000000:0:0", there's no telling whether it will
be diagnosed as a parse error, or silently accepted and truncated, in
which case, there's no telling what dom will contain.

I cringe any time I see someone using scanf to parse numbers from
arbitrary user input; I barely tolerate it for parsing things generated
by the kernel, but even there, I won't ever use scanf myself.  Same goes
for atoi.  _Only_ strtol and friends can robustly parse arbitrary input
into integers.

-- 
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: 620 bytes --]

  reply	other threads:[~2012-02-16 20:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 18:15 [Qemu-devel] [PATCH 0/2] pci devaddr parsing cleanups Michael S. Tsirkin
2012-02-16 18:15 ` [Qemu-devel] [PATCH 1/2] pci: don't export an internal function Michael S. Tsirkin
2012-02-16 18:15 ` [Qemu-devel] [PATCH 2/2] pci: rewrite devaddr parsing Michael S. Tsirkin
2012-02-16 19:23   ` malc
2012-02-16 20:39     ` Eric Blake [this message]
2012-02-16 21:35       ` malc
2012-02-17 10:08       ` Michael S. Tsirkin
2012-02-17 12:35         ` Markus Armbruster
2012-02-19 16:10           ` Michael S. Tsirkin
2012-02-19 20:03           ` Michael S. Tsirkin
2012-02-17  9:42     ` Michael S. Tsirkin
2012-02-17  9:50       ` malc
2012-02-17 10:13         ` Michael S. Tsirkin

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=4F3D6966.8090401@redhat.com \
    --to=eblake@redhat.com \
    --cc=av1474@comtv.ru \
    --cc=mst@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).