linux-kernel - Re: [PATCH v6 0/7] Fix stale IOTLB entries for kernel address space

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251017175437.GD316284@nvidia.com>
Date: Fri, 17 Oct 2025 14:54:37 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Baolu Lu <baolu.lu@...ux.intel.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>,
	Robin Murphy <robin.murphy@....com>,
	Kevin Tian <kevin.tian@...el.com>, Jann Horn <jannh@...gle.com>,
	Vasant Hegde <vasant.hegde@....com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
	Alistair Popple <apopple@...dia.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Uladzislau Rezki <urezki@...il.com>,
	Jean-Philippe Brucker <jean-philippe@...aro.org>,
	Andy Lutomirski <luto@...nel.org>, Yi Lai <yi1.lai@...el.com>,
	David Hildenbrand <david@...hat.com>,
	Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
	"Liam R . Howlett" <Liam.Howlett@...cle.com>,
	Vlastimil Babka <vbabka@...e.cz>, Mike Rapoport <rppt@...nel.org>,
	Michal Hocko <mhocko@...nel.org>,
	Matthew Wilcox <willy@...radead.org>, iommu@...ts.linux.dev,
	security@...nel.org, x86@...nel.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, "Jiang, Dave" <dave.jiang@...el.com>,
	Vinicius Costa Gomes <vinicius.gomes@...el.com>
Subject: Re: [PATCH v6 0/7] Fix stale IOTLB entries for kernel address space

On Fri, Oct 17, 2025 at 10:31:54AM -0700, Dave Hansen wrote:
> On 10/17/25 10:28, Dave Hansen wrote:
> > I'm thinking that even messing with arch_vmap_pmd_supported() would be
> > suboptimal. The easiest thing is to just stick the attached patch in
> > stable kernels and disable SVA at compile time.
> 
> Gah, please just ignore the hunks in that patch other than the
> drivers/iommu/intel/Kconfig one.

The AMD driver has to be disabled too and there is no kconfig for it.

I think it would be simpler to just patch iommu_sva_bind_device()
with like:

if (IS_ENABLED(CONFIG_X86))
   return ERR_PTR(-EOPNOTSUPP);

Jason