Kernel KVM virtualization development
 help / color / mirror / Atom feed
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,
	alhouseenyousef@gmail.com, borntraeger@linux.ibm.com,
	dtatulea@nvidia.com, junvyyang@tencent.com,
	linfeng.sun.dev@gamil.com, linfeng.sun.dev@gmail.com,
	mst@redhat.com, physicalmtea@gmail.com, slf@hdu.edu.cn,
	stable@vger.kernel.org
Subject: [GIT PULL] vhost,vdpa: last minute fixes
Date: Tue, 4 Aug 2026 17:06:24 -0400	[thread overview]
Message-ID: <20260804170624-mutt-send-email-mst@kernel.org> (raw)

The following changes since commit 075b74841bd0065a3bda3440873c747938e69b68:

  Linux 7.2-rc6 (2026-08-02 16:24:24 -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 42bc45df5905e2b7dccb72adaf7730f66cfbe03f:

  vhost-scsi: reject feature changes after endpoint (2026-08-03 23:08:15 -0400)

----------------------------------------------------------------
vhost,vdpa: last minute fixes

A small number of fixes that seem too important to
wait until the next release.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

----------------------------------------------------------------
Christian Borntraeger (1):
      vdpa/mlx5: Fix buffer length in create_direct_keys()

Jia Jia (2):
      vhost-scsi: flush backend after device ioctls
      vhost-scsi: reject feature changes after endpoint

Jun Yang (1):
      vhost: reset the vring metadata cache on vring reconfiguration

Linfeng Sun (1):
      vhost-scsi: Validate T10 PI scatterlist counts

Linfeng Sun  (1):
      vhost_iotlb: bound map allocation in add_range

Yousef Alhouseen (1):
      vhost/vdpa: reject overflowing PA map page counts on 32-bit

 drivers/vdpa/mlx5/core/mlx5_vdpa.h   |  2 ++
 drivers/vdpa/mlx5/core/mr.c          |  8 ++++--
 drivers/vdpa/mlx5/core/resources.c   | 11 ++++++++-
 drivers/vdpa/vdpa_sim/vdpa_sim.c     | 10 +++++---
 drivers/vdpa/vdpa_user/iova_domain.c | 11 ++++++++-
 drivers/vhost/iotlb.c                | 47 +++++++++++++++++++++++++-----------
 drivers/vhost/scsi.c                 | 20 ++++++++++++++-
 drivers/vhost/vdpa.c                 | 18 ++++++++++++--
 drivers/vhost/vhost.c                | 16 ++++++++++++
 9 files changed, 119 insertions(+), 24 deletions(-)


             reply	other threads:[~2026-08-04 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 21:06 Michael S. Tsirkin [this message]
2026-08-04 21:24 ` [GIT PULL] vhost,vdpa: last minute fixes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2020-10-08 20:30 Michael S. Tsirkin
2020-10-08 21:37 ` 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=20260804170624-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alhouseenyousef@gmail.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=dtatulea@nvidia.com \
    --cc=junvyyang@tencent.com \
    --cc=kvm@vger.kernel.org \
    --cc=linfeng.sun.dev@gamil.com \
    --cc=linfeng.sun.dev@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=physicalmtea@gmail.com \
    --cc=slf@hdu.edu.cn \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox