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] net: tap: check if the file descriptor is valid before using it
Date: Thu, 25 Jun 2020 09:40:10 +0200 [thread overview]
Message-ID: <570e41d1-0176-b349-20ba-367bf60416f4@redhat.com> (raw)
In-Reply-To: <d5cc729d-4010-1cf2-792d-903999df6e90@redhat.com>
On 6/25/20 9:38 AM, Laurent Vivier wrote:
> On 25/06/2020 08:19, Philippe Mathieu-Daudé wrote:
>> On 6/24/20 9:00 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, check the file descriptor is valid before passing it to qemu_set_non_block() for
>>> "fd=" and "fds=" parameters.
>>>
>>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>>> ---
>>> include/qemu/sockets.h | 1 +
>>> net/tap.c | 13 +++++++++++++
>>> util/oslib-posix.c | 5 +++++
>>> util/oslib-win32.c | 6 ++++++
>>> 4 files changed, 25 insertions(+)
>>>
>>> diff --git a/include/qemu/sockets.h b/include/qemu/sockets.h
>>> index 57cd049d6edd..5b0c2d77ddad 100644
>>> --- a/include/qemu/sockets.h
>>> +++ b/include/qemu/sockets.h
>>> @@ -17,6 +17,7 @@ int qemu_socket(int domain, int type, int protocol);
>>> 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);
>>> +bool qemu_fd_is_valid(int fd);
>>> void qemu_set_block(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..f65966aaccd8 100644
>>> --- a/net/tap.c
>>> +++ b/net/tap.c
>>> @@ -795,6 +795,12 @@ int net_init_tap(const Netdev *netdev, const char *name,
>>> return -1;
>>> }
>>>
>>> + /* Check if fd is valid */
>>> + if (!qemu_fd_is_valid(fd)) {
>>> + error_setg(errp, "Invalid file descriptor %d", fd);
>>> + return -1;
>>> + }
>>> +
>>> qemu_set_nonblock(fd);
>>>
>>> vnet_hdr = tap_probe_vnet_hdr(fd);
>>> @@ -843,6 +849,13 @@ int net_init_tap(const Netdev *netdev, const char *name,
>>> goto free_fail;
>>> }
>>>
>>> + /* Check if fd is valid */
>>> + if (!qemu_fd_is_valid(fd)) {
>>> + error_setg(errp, "Invalid file descriptor %d", fd);
>>> + ret = -1;
>>> + goto free_fail;
>>> + }
>>> +
>>> qemu_set_nonblock(fd);
>>>
>>> if (i == 0) {
>>> diff --git a/util/oslib-posix.c b/util/oslib-posix.c
>>> index 916f1be2243a..8d5705f598d3 100644
>>> --- a/util/oslib-posix.c
>>> +++ b/util/oslib-posix.c
>>> @@ -244,6 +244,11 @@ void qemu_anon_ram_free(void *ptr, size_t size)
>>> qemu_ram_munmap(-1, ptr, size);
>>> }
>>>
>>> +bool qemu_fd_is_valid(int fd)
>>> +{
>>> + return fcntl(fd, F_GETFL) != -1;
>>> +}
>>> +
>>> void qemu_set_block(int fd)
>>> {
>>> int f;
>>> diff --git a/util/oslib-win32.c b/util/oslib-win32.c
>>> index e9b14ab17847..a6be9445cfdb 100644
>>> --- a/util/oslib-win32.c
>>> +++ b/util/oslib-win32.c
>>> @@ -132,6 +132,12 @@ struct tm *localtime_r(const time_t *timep, struct tm *result)
>>> }
>>> #endif /* CONFIG_LOCALTIME_R */
>>>
>>> +bool qemu_fd_is_valid(int fd)
>>> +{
>>> + /* FIXME: how to check if fd is valid? */
>>> + return true;
>>> +}
>>
>> Maybe:
>>
>> bool qemu_fd_is_valid(int fd)
>> {
>> unsigned long res; /* ignored */
>>
>> return ioctlsocket(fd, FIONREAD, &res) == NO_ERROR;
>> }
>
> I can do that, but I have no way to test the change doesn't break
> anything... whereas always returning true ensures me it continues to
> work as before.
I'm only suggesting in case someone has a clue and way to test ;)
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-06-25 7:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 19:00 [PATCH] net: tap: check if the file descriptor is valid before using it Laurent Vivier
2020-06-25 6:19 ` Philippe Mathieu-Daudé
2020-06-25 7:38 ` Laurent Vivier
2020-06-25 7:40 ` Philippe Mathieu-Daudé [this message]
2020-06-25 8:48 ` Daniel P. Berrangé
2020-06-25 11:56 ` Laurent Vivier
2020-06-28 6:31 ` Jason Wang
2020-06-29 19:30 ` Laurent Vivier
2020-06-30 9:21 ` Jason Wang
2020-06-30 9:23 ` Daniel P. Berrangé
2020-06-30 9:31 ` Daniel P. Berrangé
2020-06-30 9:45 ` Laurent Vivier
2020-06-30 10:03 ` Jason Wang
2020-06-30 10:35 ` Laurent Vivier
2020-06-30 10:57 ` Jason Wang
2020-06-30 11:03 ` Daniel P. Berrangé
2020-06-30 12:00 ` Laurent Vivier
2020-06-30 12:35 ` Daniel P. Berrangé
2020-06-30 12:42 ` Laurent Vivier
2020-06-30 9:56 ` Jason Wang
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=570e41d1-0176-b349-20ba-367bf60416f4@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).