Re: [PATCH] [PATCH] Revert 'vfio: Delete container_q'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jason,


在 2022/10/11 2:27, Jason Gunthorpe 写道:
On Sat, Oct 08, 2022 at 05:50:31PM +0800, chenxiang wrote:
From: Xiang Chen <chenxiang66@xxxxxxxxxxxxx>

We find a issue on ARM64 platform with HNS3 VF SRIOV enabled (VFIO
passthrough in qemu):
kill the qemu thread, then echo 0 > sriov_numvfs to disable sriov
immediately, sometimes we will see following warnings:
I suspect this is fixed in vfio-next now, in a different way. Please check

Can you point out which patches fix it?
I need to merge back those patches to our version, then have a test.


After removing container_q, arm_smmu_release_dev() caused by disabling
sriov may occur before arm_smmuv3_attach_dev() called by echo 0 > sriov_numvfs,
and arm_smmu_attach_dev() may refer to freed iommu_fwspec, so it causes
above warnings.
Which is the same effective issue s390 hit already.

It is interesting that container_q was solving this, that seems to be
a inadverent side effect nobody noticed.

Jason
.





[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux