From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Stefan Weil" <sw@weilnetz.de>,
"Jason Wang" <jasowang@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v3 1/2] net: tap: check if the file descriptor is valid before using it
Date: Mon, 6 Jul 2020 10:45:25 +0200 [thread overview]
Message-ID: <b97672d9-c0a2-bd27-3421-c6b276434a7f@redhat.com> (raw)
In-Reply-To: <31892cf3-b19c-9911-8fed-1dd5dcbec2c0@redhat.com>
On 7/2/20 10:18 AM, Philippe Mathieu-Daudé wrote:
> On 7/2/20 10:17 AM, Laurent Vivier wrote:
>> On 02/07/2020 10:00, Philippe Mathieu-Daudé wrote:
>>> On 7/1/20 9:39 PM, Laurent Vivier wrote:
>>>> qemu_set_nonblock() checks that the file descriptor can be used and, if
>>>> not, crashes QEMU. An assert() is used for that. The use of assert() is
>>>> used to detect programming error and the coredump will allow to debug
>>>> the problem.
>>>>
>>>> But in the case of the tap device, this assert() can be triggered by
>>>> a misconfiguration by the user. At startup, it's not a real problem, but it
>>>> can also happen during the hot-plug of a new device, and here it's a
>>>> problem because we can crash a perfectly healthy system.
>>>>
>>>> For instance:
>>>> # ip link add link virbr0 name macvtap0 type macvtap mode bridge
>>>> # ip link set macvtap0 up
>>>> # TAP=/dev/tap$(ip -o link show macvtap0 | cut -d: -f1)
>>>> # qemu-system-x86_64 -machine q35 -device pcie-root-port,id=pcie-root-port-0 -monitor stdio 9<> $TAP
>>>> (qemu) netdev_add type=tap,id=hostnet0,vhost=on,fd=9
>>>> (qemu) device_add driver=virtio-net-pci,netdev=hostnet0,id=net0,bus=pcie-root-port-0
>>>> (qemu) device_del net0
>>>> (qemu) netdev_del hostnet0
>>>> (qemu) netdev_add type=tap,id=hostnet1,vhost=on,fd=9
>>>> qemu-system-x86_64: .../util/oslib-posix.c:247: qemu_set_nonblock: Assertion `f != -1' failed.
>>>> Aborted (core dumped)
>>>>
>>>> To avoid that, add a function, qemu_try_set_nonblock(), that allows to report the
>>>> problem without crashing.
>>>>
>>>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>>>> ---
>>>> include/qemu/sockets.h | 1 +
>>>> net/tap.c | 16 +++++++++---
>>>> util/oslib-posix.c | 26 +++++++++++++------
>>>> util/oslib-win32.c | 57 ++++++++++++++++++++++++------------------
>>>> 4 files changed, 64 insertions(+), 36 deletions(-)
>>>>
>>>> diff --git a/include/qemu/sockets.h b/include/qemu/sockets.h
>>>> index 57cd049d6edd..7d1f8135767d 100644
>>>> --- a/include/qemu/sockets.h
>>>> +++ b/include/qemu/sockets.h
>>>> @@ -18,6 +18,7 @@ int qemu_accept(int s, struct sockaddr *addr, socklen_t *addrlen);
>>>> int socket_set_cork(int fd, int v);
>>>> int socket_set_nodelay(int fd);
>>>> void qemu_set_block(int fd);
>>>> +int qemu_try_set_nonblock(int fd);
>>>> void qemu_set_nonblock(int fd);
>>>> int socket_set_fast_reuse(int fd);
>>>>
>>>> diff --git a/net/tap.c b/net/tap.c
>>>> index 6207f61f84ab..fb04c9044ce2 100644
>>>> --- a/net/tap.c
>>>> +++ b/net/tap.c
>>>> @@ -766,6 +766,7 @@ int net_init_tap(const Netdev *netdev, const char *name,
>>>> Error *err = NULL;
>>>> const char *vhostfdname;
>>>> char ifname[128];
>>>> + int ret = 0;
>>>
>>> No need to zero-initialize.
>>>
>>> Otherwise:
>>> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>>>
>>
>> I would agree with you but gcc doesn't:
>>
>> net/tap.c:769:9: error: ‘ret’ may be used uninitialized in this function
>> [-Werror=maybe-uninitialized]
>> 769 | int ret;
>> | ^~~
>
> I tried to outsmart GCC by manual review :/
IOW my R-b stands:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>
>>
>> if nfds == 0, we don't enter in the loop and ret is never set.
>>
>> Thanks,
>> Laurent
>>
>
next prev parent reply other threads:[~2020-07-06 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 19:39 [PATCH v3 0/2] net: tap: check file descriptor can be used Laurent Vivier
2020-07-01 19:39 ` [PATCH v3 1/2] net: tap: check if the file descriptor is valid before using it Laurent Vivier
2020-07-02 8:00 ` Philippe Mathieu-Daudé
2020-07-02 8:17 ` Laurent Vivier
2020-07-02 8:18 ` Philippe Mathieu-Daudé
2020-07-06 8:45 ` Philippe Mathieu-Daudé [this message]
2020-07-07 7:56 ` Jason Wang
2020-07-07 10:21 ` Laurent Vivier
2020-07-01 19:39 ` [PATCH v3 2/2] net: detect errors from probing vnet hdr flag for TAP devices Laurent Vivier
2020-07-06 8:47 ` Philippe Mathieu-Daudé
2020-07-06 8:21 ` [PATCH v3 0/2] net: tap: check file descriptor can be used 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=b97672d9-c0a2-bd27-3421-c6b276434a7f@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).