Thread (48 messages) 48 messages, 6 authors, 2026-04-10

RE: [PATCH v2 0/7] iommu/arm-smmu-v3: Quarantine device upon ATC invalidation timeout

From: "Tian, Kevin" <kevin.tian@intel.com>
Date: 2026-03-25 06:55:46
Also in: linux-acpi, linux-iommu, linux-pci, lkml

From: Jason Gunthorpe <jgg@nvidia.com>
Sent: Tuesday, March 24, 2026 8:03 AM

On Wed, Mar 18, 2026 at 08:10:01PM -0700, Nicolin Chen wrote:
quoted
On Thu, Mar 19, 2026 at 02:29:38AM +0000, Tian, Kevin wrote:
quoted
quoted
quoted
quoted
This series addresses a critical vulnerability and stability issue where
an
quoted
quoted
quoted
quoted
quoted
unresponsive PCIe device failing to process ATC (Address Translation
Cache)
quoted
quoted
invalidation requests leads to silent data corruption and continuous
SMMU
quoted
quoted
CMDQ error spam.
None of the patches in this series contains a Fixed tag and cc stable.
Hmm, I guess AI overly polished the cover letter so it sounds too
strong?

This is essentially a vulnerability (potential memory corruption).
And none of these patches actually fixes any regression. The PATCH
7 even requires the arm_smmu_invs series which has not been merged
yet :-/
Fixes tag and backporting are not just for regression. People certainly
want to see reported vulnerabilities fixed in stable kernels...
Well, maybe I'll just leave additional line telling people that this
can't be a bug "fix" because it's written on another unmerged series?
I think this is more of a feature (RAS support for SMMUv3) than a
specific fix.
Not a RAS guy, but below is what I got from AI:

"
RAS improvements typically involve better error reporting, graceful
degradation, or improved recovery - but they usually don't involve
scenarios where the system continues operating with compromised
security assumptions."
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help