From: Greg KH <gregkh@linuxfoundation.org>
To: Ban ZuoXiang <bbaa@bbaa.fun>
Cc: Baolu Lu <baolu.lu@linux.intel.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [REGRESSION][BISECTED] PCI Passthrough / SR-IOV Failure on Stable Kernel ≥ v6.12.35
Date: Wed, 23 Jul 2025 11:39:33 +0200 [thread overview]
Message-ID: <2025072314-malformed-antler-2829@gregkh> (raw)
In-Reply-To: <82255DF0A021BC1D+513c6ded-088b-4799-8605-b7118c7713ef@bbaa.fun>
On Wed, Jul 23, 2025 at 05:22:44PM +0800, Ban ZuoXiang wrote:
> > Nope! We need your help as you are the one that can reproduce it :)
> >
> > Are we missing a backport? Did we get the backport incorrect? Should
> > we just revert it?
> >
> > thanks,
> > greg k-h
>
> Hi, greg k-h
>
> Original patch:
>
> > diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> > index bb871674d8acba..226e174577fff1 100644
> > --- a/drivers/iommu/intel/iommu.c
> > +++ b/drivers/iommu/intel/iommu.c
> > @@ -4298,6 +4306,9 @@ static int identity_domain_attach_dev(struct
> > iommu_domain *domain, struct device
> > else
> > ret = device_setup_pass_through(dev);
> >
> > + if (!ret)
> > + info->domain_attached = true;
> > +
> > return ret;
> > }
> Backport patch:
> > diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> > index 157542c07aaafa..56e9f125cda9a0 100644
> > --- a/drivers/iommu/intel/iommu.c
> > +++ b/drivers/iommu/intel/iommu.c
> > @@ -4406,6 +4414,9 @@ static int device_set_dirty_tracking(struct
> > list_head *devices, bool enable)
> > break;
> > }
> >
> > + if (!ret)
> > + info->domain_attached = true;
> > +
> > return ret;
> > }
>
> The last hunk of the original patch [1] was applied to the
> |identity_domain_attach_dev| function,
> but the last hunk of the backport patch [2] appears to have been
> mistakenly applied to the |device_set_dirty_tracking| function.
> I can confirm that correctly placing the patch from
> device_set_dirty_tracking into identity_domain_attach_dev resolves the
> issue.
>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=320302baed05c6456164652541f23d2a96522c06
> [2]
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fb5873b779dd5858123c19bbd6959566771e2e83
Ah, nice work!
Can you send a patch that fixes this up properly please? I'll be glad
to queue that up.
greg k-h
prev parent reply other threads:[~2025-07-23 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 9:59 [REGRESSION][BISECTED] PCI Passthrough / SR-IOV Failure on Stable Kernel ≥ v6.12.35 Ban ZuoXiang
2025-07-22 1:30 ` Baolu Lu
2025-07-22 2:40 ` bbaa
2025-07-22 13:14 ` Ban ZuoXiang
2025-07-22 13:19 ` Greg KH
2025-07-23 9:22 ` Ban ZuoXiang
2025-07-23 9:39 ` Greg KH [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=2025072314-malformed-antler-2829@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=baolu.lu@linux.intel.com \
--cc=bbaa@bbaa.fun \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox