From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
acme@kernel.org, gshan@redhat.com, jasowang@redhat.com,
jie.deng@intel.com, krzysztof.kozlowski@linaro.org,
lingshan.zhu@intel.com, mst@redhat.com, namhyung@kernel.org,
stable@kernel.org, xianting.tian@linux.alibaba.com,
yihyu@redhat.com
Subject: [GIT PULL] virtio: bugfixes
Date: Sun, 14 Apr 2024 04:20:47 -0400 [thread overview]
Message-ID: <20240414042047-mutt-send-email-mst@kernel.org> (raw)
The following changes since commit fec50db7033ea478773b159e0e2efb135270e3b7:
Linux 6.9-rc3 (2024-04-07 13:22:46 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
for you to fetch changes up to 76f408535aab39c33e0a1dcada9fba5631c65595:
vhost: correct misleading printing information (2024-04-08 04:11:04 -0400)
----------------------------------------------------------------
virtio: bugfixes
Some small, obvious (in hindsight) bugfixes:
- new ioctl in vhost-vdpa has a wrong # - not too late to fix
- vhost has apparently been lacking an smp_rmb() -
due to code duplication :( The duplication will be fixed in
the next merge cycle, this is a minimal fix.
- an error message in vhost talks about guest moving used index -
which of course never happens, guest only ever moves the
available index.
- i2c-virtio didn't set the driver owner so it did not get
refcounted correctly.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
----------------------------------------------------------------
Gavin Shan (2):
vhost: Add smp_rmb() in vhost_vq_avail_empty()
vhost: Add smp_rmb() in vhost_enable_notify()
Krzysztof Kozlowski (1):
virtio: store owner from modules with register_virtio_driver()
Michael S. Tsirkin (1):
vhost-vdpa: change ioctl # for VDPA_GET_VRING_SIZE
Xianting Tian (1):
vhost: correct misleading printing information
.../driver-api/virtio/writing_virtio_drivers.rst | 1 -
drivers/vhost/vhost.c | 30 ++++++++++++++++++----
drivers/virtio/virtio.c | 6 +++--
include/linux/virtio.h | 7 +++--
include/uapi/linux/vhost.h | 15 ++++++-----
5 files changed, 42 insertions(+), 17 deletions(-)
next reply other threads:[~2024-04-14 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 8:20 Michael S. Tsirkin [this message]
2024-04-14 17:12 ` [GIT PULL] virtio: bugfixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-11-11 13:50 Michael S. Tsirkin
2024-11-12 18:07 ` pr-tracker-bot
2024-10-07 15:51 Michael S. Tsirkin
2024-10-07 18:37 ` pr-tracker-bot
2023-12-25 13:27 Michael S. Tsirkin
2023-12-25 23:32 ` pr-tracker-bot
2023-08-13 23:08 Michael S. Tsirkin
2023-08-15 6:30 ` pr-tracker-bot
2020-08-26 13:27 Michael S. Tsirkin
2020-08-26 18:34 ` pr-tracker-bot
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=20240414042047-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=acme@kernel.org \
--cc=gshan@redhat.com \
--cc=jasowang@redhat.com \
--cc=jie.deng@intel.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xianting.tian@linux.alibaba.com \
--cc=yihyu@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).