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,
brauner@kernel.org, dan.carpenter@linaro.org, elver@google.com,
jasowang@redhat.com, lkp@intel.com, luigi.leonardi@outlook.com,
michael.christie@oracle.com, mst@redhat.com, schalla@marvell.com,
sgarzare@redhat.com,
syzbot+8a02104389c2e0ef5049@syzkaller.appspotmail.com,
wh1sper@zju.edu.cn
Subject: [GIT PULL] virtio: bugfixes
Date: Mon, 7 Oct 2024 11:51:58 -0400 [thread overview]
Message-ID: <20241007115158-mutt-send-email-mst@kernel.org> (raw)
The following changes since commit efcd71af38be403fa52223092f79ada446e121ba:
vsock/virtio: avoid queuing packets when intermediate queue is empty (2024-09-25 07:07:44 -0400)
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 221af82f606d928ccef19a16d35633c63026f1be:
vhost/scsi: null-ptr-dereference in vhost_scsi_get_req() (2024-10-07 11:47:56 -0400)
----------------------------------------------------------------
virtio: bugfixes
Several small bugfixes all over the place.
Most notably, fixes the vsock allocation with GFP_KERNEL in atomic
context, which has been triggering warnings for lots of testers.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
----------------------------------------------------------------
Haoran Zhang (1):
vhost/scsi: null-ptr-dereference in vhost_scsi_get_req()
Michael S. Tsirkin (3):
virtio_ring: tag event_triggered as racy for KCSAN
virtio_console: fix misc probe bugs
vsock/virtio: use GFP_ATOMIC under RCU read lock
Srujana Challa (1):
vdpa/octeon_ep: Fix format specifier for pointers in debug messages
drivers/char/virtio_console.c | 18 ++++++++++--------
drivers/vdpa/octeon_ep/octep_vdpa_hw.c | 12 ++++++------
drivers/vhost/scsi.c | 25 ++++++++++++++-----------
drivers/virtio/virtio_ring.c | 2 +-
net/vmw_vsock/virtio_transport.c | 8 ++++----
5 files changed, 35 insertions(+), 30 deletions(-)
next reply other threads:[~2024-10-07 15:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 15:51 Michael S. Tsirkin [this message]
2024-10-07 18:37 ` [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-04-14 8:20 Michael S. Tsirkin
2024-04-14 17:12 ` 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-13 23:08 ` Michael S. Tsirkin
2023-08-15 6:30 ` pr-tracker-bot
2023-08-15 6:30 ` pr-tracker-bot
2020-08-26 13:27 Michael S. Tsirkin
2020-08-26 13:27 ` Michael S. Tsirkin
2020-08-26 18:34 ` pr-tracker-bot
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=20241007115158-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=brauner@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=elver@google.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luigi.leonardi@outlook.com \
--cc=michael.christie@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=schalla@marvell.com \
--cc=sgarzare@redhat.com \
--cc=syzbot+8a02104389c2e0ef5049@syzkaller.appspotmail.com \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wh1sper@zju.edu.cn \
/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.