All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: "Srivastava, Dheeraj Kumar" <dhsrivas@amd.com>
Cc: <joro@8bytes.org>, <afael@kernel.org>, <bhelgaas@google.com>,
	<alex@shazbot.org>, <jgg@nvidia.com>, <will@kernel.org>,
	<robin.murphy@arm.com>, <lenb@kernel.org>, <kevin.tian@intel.com>,
	<baolu.lu@linux.intel.com>,
	<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
	<linux-pci@vger.kernel.org>, <kvm@vger.kernel.org>,
	<patches@lists.linux.dev>, <pjaroszynski@nvidia.com>,
	<vsethi@nvidia.com>, <helgaas@kernel.org>, <etzhao1900@gmail.com>
Subject: Re: [PATCH v7 1/5] iommu: Lock group->mutex in iommu_deferred_attach()
Date: Wed, 26 Nov 2025 08:16:54 -0800	[thread overview]
Message-ID: <aScn9t5ctN7FgRKD@Asurada-Nvidia> (raw)
In-Reply-To: <1f65de37-db9f-4807-a3ff-6cd377c855a5@amd.com>

On Wed, Nov 26, 2025 at 06:25:34PM +0530, Srivastava, Dheeraj Kumar wrote:
> On 11/22/2025 7:27 AM, Nicolin Chen wrote:
> > The iommu_deferred_attach() function invokes __iommu_attach_device(), but
> > doesn't hold the group->mutex like other __iommu_attach_device() callers.
> > 
> > Though there is no pratical bug being triggered so far, it would be better
> > to apply the same locking to this __iommu_attach_device(), since the IOMMU
> > drivers nowaday are more aware of the group->mutex -- some of them use the
> > iommu_group_mutex_assert() function that could be potentially in the path
> > of an attach_dev callback function invoked by the __iommu_attach_device().
> > 
> > Worth mentioning that the iommu_deferred_attach() will soon need to check
> > group->resetting_domain that must be locked also.
> > 
> > Thus, grab the mutex to guard __iommu_attach_device() like other callers.
> > 
> 
> Tested the series with PCI reset on PFs and VFs, including device
> pass-through to a Linux guest. All scenarios worked as expected.
> 
> Tested-by: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>

Thanks for testing!

Yet, this is replying to PATCH-1. So, you might want to reply with
your "Tested-by" tag to PATCH-0 :)

Otherwise, default B4 command might miss your tag in other patches:

  ✗ [PATCH v7 1/5] iommu: Lock group->mutex in iommu_deferred_attach()
    + Tested-by: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com> (✓ DKIM/amd.com)
  ✗ [PATCH v7 2/5] iommu: Tidy domain for iommu_setup_dma_ops()
    + Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> (✗ DKIM/Nvidia.com)
  ✗ [PATCH v7 3/5] iommu: Add iommu_driver_get_domain_for_dev() helper
    + Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> (✗ DKIM/Nvidia.com)
  ✗ [PATCH v7 4/5] iommu: Introduce pci_dev_reset_iommu_prepare/done()
    + Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> (✗ DKIM/Nvidia.com)
  ✗ [PATCH v7 5/5] PCI: Suspend iommu function prior to resetting a device
    + Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> (✗ DKIM/Nvidia.com)

Thank you
Nicolin

  reply	other threads:[~2025-11-26 16:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-22  1:57 [PATCH v7 0/5] Disable ATS via iommu during PCI resets Nicolin Chen
2025-11-22  1:57 ` [PATCH v7 1/5] iommu: Lock group->mutex in iommu_deferred_attach() Nicolin Chen
2025-11-26 12:55   ` Srivastava, Dheeraj Kumar
2025-11-26 16:16     ` Nicolin Chen [this message]
2025-11-26 16:19       ` Dheeraj Kumar Srivastava
2025-11-22  1:57 ` [PATCH v7 2/5] iommu: Tidy domain for iommu_setup_dma_ops() Nicolin Chen
2025-11-25 19:19   ` Jason Gunthorpe
2025-11-22  1:57 ` [PATCH v7 3/5] iommu: Add iommu_driver_get_domain_for_dev() helper Nicolin Chen
2025-11-25 19:21   ` Jason Gunthorpe
2025-11-22  1:57 ` [PATCH v7 4/5] iommu: Introduce pci_dev_reset_iommu_prepare/done() Nicolin Chen
2025-11-25 19:27   ` Jason Gunthorpe
2025-11-22  1:57 ` [PATCH v7 5/5] PCI: Suspend iommu function prior to resetting a device Nicolin Chen
2025-11-25 19:28   ` Jason Gunthorpe
2025-11-26 21:43   ` Bjorn Helgaas
2025-11-26 21:51     ` Nicolin Chen
2025-11-25 14:22 ` [PATCH v7 0/5] Disable ATS via iommu during PCI resets Jörg Rödel
2025-11-25 18:30   ` Nicolin Chen
2025-11-26 16:21 ` Srivastava, Dheeraj Kumar

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=aScn9t5ctN7FgRKD@Asurada-Nvidia \
    --to=nicolinc@nvidia.com \
    --cc=afael@kernel.org \
    --cc=alex@shazbot.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=dhsrivas@amd.com \
    --cc=etzhao1900@gmail.com \
    --cc=helgaas@kernel.org \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=pjaroszynski@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=vsethi@nvidia.com \
    --cc=will@kernel.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 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.