All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Vipin Sharma" <vipinsh@google.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v4 15/16] vfio: selftests: Verify that opening VFIO device fails during Live Update
Date: Wed, 13 May 2026 23:33:36 +0000	[thread overview]
Message-ID: <20260513233336.D51CDC19425@smtp.kernel.org> (raw)
In-Reply-To: <20260511234802.2280368-16-vipinsh@google.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Unconditionally testing all legacy IOMMU modes will cause the selftest to crash on kernels lacking legacy VFIO support.
--

commit 15d06d7e17051c89eae8198f7b5a759b9968ab87
Author: David Matlack <dmatlack@google.com>

vfio: selftests: Verify that opening VFIO device fails during Live Update

Verify that opening a VFIO device through its cdev file and via
VFIO_GROUP_GET_DEVICE_FD both fail with -EBUSY if the device was
preserved across a Live Update.

> diff --git a/tools/testing/selftests/vfio/vfio_pci_liveupdate_kexec_test.c b/tools/testing/selftests/vfio/vfio_pci_liveupdate_kexec_test.c
> index 15b3e3af91d1e..65c48196e44e7 100644
> --- a/tools/testing/selftests/vfio/vfio_pci_liveupdate_kexec_test.c
> +++ b/tools/testing/selftests/vfio/vfio_pci_liveupdate_kexec_test.c

[ ... ]

> @@ -36,6 +36,42 @@ static void before_kexec(int luo_fd)
>  	daemonize_and_wait();
>  }
>  
> +static void check_open_vfio_device_fails(void)
> +{

[ ... ]

> +	for (i = 0; i < nr_iommu_modes; i++) {
> +		if (!iommu_modes[i].container_path)
> +			continue;
> +
> +		iommu = iommu_init(iommu_modes[i].name);

Does this introduce a regression on kernels lacking legacy VFIO support?

If the kernel is compiled without legacy VFIO support (CONFIG_VFIO_GROUP=n),
calling iommu_init() on a legacy container path like /dev/vfio/vfio will
fail.

This causes iommu_init() to fail its internal assertion, calling
VFIO_LOG_AND_EXIT() and aborting the process. Because this standalone test
program does not use kselftest_harness process isolation, crashing here
prevents it from verifying the core live update functionality.

Could we verify the container path is accessible before calling iommu_init()
so unsupported modes can be gracefully skipped?

> +
> +		device = vfio_pci_device_alloc(device_bdf, iommu);

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260511234802.2280368-1-vipinsh@google.com?part=15

  reply	other threads:[~2026-05-13 23:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 23:47 [PATCH v4 00/16] vfio/pci: Base Live Update support for VFIO Vipin Sharma
2026-05-11 23:47 ` [PATCH v4 01/16] vfio/pci: Register a file handler with Live Update Orchestrator Vipin Sharma
2026-05-13  2:44   ` sashiko-bot
2026-05-11 23:47 ` [PATCH v4 02/16] vfio/pci: Preserve vfio-pci device files across Live Update Vipin Sharma
2026-05-12 20:59   ` David Matlack
2026-05-12 21:29     ` Vipin Sharma
2026-05-13 22:42       ` Samiullah Khawaja
2026-05-14 15:24         ` Pratyush Yadav
2026-05-13  3:24   ` sashiko-bot
2026-05-11 23:47 ` [PATCH v4 03/16] vfio/pci: Retrieve preserved device files after " Vipin Sharma
2026-05-13  4:23   ` sashiko-bot
2026-05-11 23:47 ` [PATCH v4 04/16] vfio/pci: Notify PCI subsystem about devices preserved across " Vipin Sharma
2026-05-11 23:47 ` [PATCH v4 05/16] vfio: Enforce preserved devices are retrieved via LIVEUPDATE_SESSION_RETRIEVE_FD Vipin Sharma
2026-05-13 19:16   ` sashiko-bot
2026-05-11 23:47 ` [PATCH v4 06/16] vfio/pci: Store incoming Live Update state in struct vfio_pci_core_device Vipin Sharma
2026-05-13 20:13   ` sashiko-bot
2026-05-11 23:47 ` [PATCH v4 07/16] docs: liveupdate: Add documentation for VFIO PCI Vipin Sharma
2026-05-11 23:47 ` [PATCH v4 08/16] vfio: selftests: Build liveupdate library in VFIO selftests Vipin Sharma
2026-05-13 20:28   ` sashiko-bot
2026-05-11 23:47 ` [PATCH v4 09/16] vfio: selftests: Add vfio_pci_liveupdate_uapi_test Vipin Sharma
2026-05-13 21:12   ` sashiko-bot
2026-05-11 23:47 ` [PATCH v4 10/16] vfio: selftests: Initialize vfio_pci_device using a VFIO cdev FD Vipin Sharma
2026-05-11 23:47 ` [PATCH v4 11/16] vfio: selftests: Add Makefile support for TEST_GEN_PROGS_EXTENDED Vipin Sharma
2026-05-11 23:47 ` [PATCH v4 12/16] vfio: selftests: Add vfio_pci_liveupdate_kexec_test Vipin Sharma
2026-05-11 23:47 ` [PATCH v4 13/16] vfio: selftests: Expose iommu_modes to tests Vipin Sharma
2026-05-11 23:48 ` [PATCH v4 14/16] vfio: selftests: Expose low-level helper routines for setting up struct vfio_pci_device Vipin Sharma
2026-05-11 23:48 ` [PATCH v4 15/16] vfio: selftests: Verify that opening VFIO device fails during Live Update Vipin Sharma
2026-05-13 23:33   ` sashiko-bot [this message]
2026-05-11 23:48 ` [PATCH v4 16/16] vfio: selftests: Add continuous DMA to vfio_pci_liveupdate_kexec_test Vipin Sharma
2026-05-13 23:22   ` sashiko-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=20260513233336.D51CDC19425@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vipinsh@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.