From: Jakub Jermar <1769067@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1769067] [NEW] virtio-net ignores the absence of the VIRTIO_NET_F_CTRL_VQ feature bit
Date: Fri, 04 May 2018 07:15:23 -0000 [thread overview]
Message-ID: <152541812417.6750.13037728534674633876.malonedeb@wampee.canonical.com> (raw)
Public bug reported:
When negotiating virtio-net feature bits, the device ignores the absence
of the VIRTIO_NET_F_CTRL_VQ bit in driver feature bits and provides
three virtqueues, including the control virtqueue, even though the
driver is expecting only the receive and transmit virtqueues. Looking
into the source code, it appears it always assumes the presence of the
control virtqueue, violating thus the VIRTIO version 1.0 specification.
** Affects: qemu
Importance: Undecided
Status: New
** Tags: virtio virtio-net
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1769067
Title:
virtio-net ignores the absence of the VIRTIO_NET_F_CTRL_VQ feature bit
Status in QEMU:
New
Bug description:
When negotiating virtio-net feature bits, the device ignores the
absence of the VIRTIO_NET_F_CTRL_VQ bit in driver feature bits and
provides three virtqueues, including the control virtqueue, even
though the driver is expecting only the receive and transmit
virtqueues. Looking into the source code, it appears it always assumes
the presence of the control virtqueue, violating thus the VIRTIO
version 1.0 specification.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1769067/+subscriptions
next reply other threads:[~2018-05-04 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 7:15 Jakub Jermar [this message]
2021-05-05 8:19 ` [Bug 1769067] Re: virtio-net ignores the absence of the VIRTIO_NET_F_CTRL_VQ feature bit Thomas Huth
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=152541812417.6750.13037728534674633876.malonedeb@wampee.canonical.com \
--to=1769067@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.