From: Li Qiang <liq3ea@163.com>
To: thuth@redhat.com, lvivier@redhat.com, pbonzini@redhat.com,
mst@redhat.com, peter.maydell@linaro.org,
marcandre.lureau@redhat.com, berrange@redhat.com,
jasowang@redhat.com
Cc: liq3ea@gmail.com, qemu-devel@nongnu.org, Li Qiang <liq3ea@163.com>
Subject: [Qemu-devel] [PATCH 0/3] vhost-user-test fix
Date: Fri, 14 Dec 2018 17:26:22 -0800 [thread overview]
Message-ID: <20181215012625.73315-1-liq3ea@163.com> (raw)
Currently, the vhost-user-test is not correct.
When in qtest mode, the accel is qtest, not kvm.
So when the client side of vhost-user-test send
'VHOST_USER_SET_VRING_CALL' msg, the 'fd' will
no be added in 'fds' in 'vhost_set_vring_file'.
In 'chr_read' of the server side in the
vhost-user-test, it calls 'qemu_chr_fe_get_msgfds'
to get the fd in 'VHOST_USER_SET_VRING_CALL'. Though
there is no fd returned, but as the 'fd' is not initialized
so 'fd' maybe valid, and 'qemu_set_nonblock' will be success.
Even worse, 'qemu_set_nonblock' doesn't check the return value
of fcntl.
So this cause the interesting bug here: there are three issues,
but they combined and will bypass the qtest.
This patchset tries to address these issue.
Li Qiang (3):
tests: vhost-user-test: initialize 'fd' in chr_read
vhost-user: add fds inf 'vhost_set_vring_file' in qtest
util: check the return value of fcntl in qemu_set_{block, nonblock}
hw/virtio/vhost-user.c | 3 ++-
tests/vhost-user-test.c | 2 +-
util/oslib-posix.c | 8 ++++++--
3 files changed, 9 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2018-12-15 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 1:26 Li Qiang [this message]
2018-12-15 1:26 ` [Qemu-devel] [PATCH 1/3] tests: vhost-user-test: initialize 'fd' in chr_read Li Qiang
2018-12-15 1:26 ` [Qemu-devel] [PATCH 2/3] vhost-user: add fds inf 'vhost_set_vring_file' in qtest Li Qiang
2018-12-15 11:08 ` Paolo Bonzini
2018-12-15 1:26 ` [Qemu-devel] [PATCH 3/3] util: check the return value of fcntl in qemu_set_{block, nonblock} Li Qiang
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=20181215012625.73315-1-liq3ea@163.com \
--to=liq3ea@163.com \
--cc=berrange@redhat.com \
--cc=jasowang@redhat.com \
--cc=liq3ea@gmail.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).