From: Alex Williamson <alex@shazbot.org>
To: Raghavendra Rao Ananta <rananta@google.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
Alex Williamson <alex.williamson@redhat.com>,
Longfang Liu <liulongfang@huawei.com>,
David Matlack <dmatlack@google.com>,
Josh Hilke <jrhilke@google.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] vfio: Fixes in iommufd vfio token handling
Date: Thu, 6 Nov 2025 21:34:59 -0700 [thread overview]
Message-ID: <20251106213459.3c2a59a8.alex@shazbot.org> (raw)
In-Reply-To: <20251031170603.2260022-1-rananta@google.com>
On Fri, 31 Oct 2025 17:06:01 +0000
Raghavendra Rao Ananta <rananta@google.com> wrote:
> Hello,
>
> The series includes a couple of bug fixes that were accidentally
> introduced as a part of VFIO's vf_token management for iommufd.
>
> Patch-1: Fixes ksize arg while copying user struct in
> vfio_df_ioctl_bind_iommufd.
>
> Patch-2: Adds missing .match_token_uuid callback in
> hisi_acc_vfio_pci_migrn_ops.
>
> Thank you.
> Raghavendra
>
> Raghavendra Rao Ananta (2):
> vfio: Fix ksize arg while copying user struct in
> vfio_df_ioctl_bind_iommufd()
> hisi_acc_vfio_pci: Add .match_token_uuid callback in
> hisi_acc_vfio_pci_migrn_ops
>
> drivers/vfio/device_cdev.c | 2 +-
> drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
>
> base-commit: 3a8660878839faadb4f1a6dd72c3179c1df56787
Applied to vfio next branch for v6.19. Thanks,
Alex
prev parent reply other threads:[~2025-11-07 4:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 17:06 [PATCH v2 0/2] vfio: Fixes in iommufd vfio token handling Raghavendra Rao Ananta
2025-10-31 17:06 ` [PATCH v2 1/2] vfio: Fix ksize arg while copying user struct in vfio_df_ioctl_bind_iommufd() Raghavendra Rao Ananta
2025-10-31 17:06 ` [PATCH v2 2/2] hisi_acc_vfio_pci: Add .match_token_uuid callback in hisi_acc_vfio_pci_migrn_ops Raghavendra Rao Ananta
2025-10-31 17:08 ` Jason Gunthorpe
2025-11-03 1:14 ` liulongfang
2025-11-07 4:34 ` Alex Williamson [this message]
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=20251106213459.3c2a59a8.alex@shazbot.org \
--to=alex@shazbot.org \
--cc=alex.williamson@redhat.com \
--cc=dmatlack@google.com \
--cc=jgg@ziepe.ca \
--cc=jrhilke@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=rananta@google.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 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.