          mail domains are different
 -0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
  0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily
                             valid
 -1.0 MAILING_LIST_MULTI     Multiple indicators imply a widely-seen list
                             manager
 -0.1 DKIMWL_WL_HIGH         DKIMwl.org - High trust sender
SpamTally: Final spam score: 24

On 1/21/26 13:26, Mario Limonciello wrote:
> 
> 
> On 1/20/26 8:08 PM, Mario Limonciello wrote:
>> Hi,
>>
>> Recently I found out that amdxdna stopped working in linux-6.18.4.  
>> This is because of this commit in linux-6.18.y:
>>
>> commit c341dee80b5d ("iommu: disable SVA when CONFIG_X86 is set")
>>
>> That was originally backported from upstream:
>>
>> commit 72f98ef9a4be ("iommu: disable SVA when CONFIG_X86 is set")
>>
>> ---
>>
>> SVA support is a requirement for amdxdna.
>>
>> The series that this commit came from was part of a larger 8 patch 
>> series, but this was the only commit that was CC'ed to stable.
>>
>> As a result this is not broken in 6.19-rc, but it is broken in 
>> linux-6.18.y (and presumably any older stable kernels still around 
>> that picked it up).
>>
>> So there are two options I see:
>>
>> 1) Revert c341dee80b5d in linux-6.18.y (and any other stable kernel 
>> that picked it up but has amdxdna)
>>
>> 2) Bring the entire 8 patch series to linux-6.18.y.
>>
>> This is the entire series (I didn't look up the hashes from mainline, 
>> but they should have all landed):
>> https://lore.kernel.org/linux-iommu/20251022082635.2462433-1- 
>> baolu.lu@linux.intel.com/
>>
>> What should we do?
>>
> 
> If the decision is to take the remaining commits to 6.18.y to fix this I 
> did confirm they cleanly cherry pick and build.Â  Here are the hashes.
> 
> commit 27bfafac65d8 ("mm: add a ptdesc flag to mark kernel page tables")
> commit 977870522af3 ("mm: actually mark kernel page table pages")
> commit 412d000346ea ("x86/mm: use 'ptdesc' when freeing PMD pages")
> commit 018942956723 ("mm: introduce pure page table freeing function")
> commit bf9e4e30f353 ("x86/mm: use pagetable_free()")
> commit 5ba2f0a15564 ("mm: introduce deferred freeing for kernel page 
> tables")
> commit e37d5a2d60a3 ("iommu/sva: invalidate stale IOTLB entries for 
> kernel address space")
> 

Yes. These patches fix a security issue in iommu/sva on x86 and restore
the SVA functionality.

Thanks,
baolu


From - Wed Jan 21 07:28:08 2026
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Return-Path: <stable+bounces-210709-hi=josie.lol@vger.kernel.org>
Delivered-To: hi@josie.lol
Received: from witcher.mxrouting.net
	by witcher.mxrouting.net with LMTP
	id QP+qFQSAcGl1UyoAYBR5ng
	(envelope-from <stable+bounces-210709-hi=josie.lol@vger.kernel.org>)
	for <hi@josie.lol>; Wed, 21 Jan 2026 07:28:04 +0000
Return-path: <stable+bounces-210709-hi=josie.lol@vger.kernel.org>
Envelope-to: hi@josie.lol
Delivery-date: Wed, 21 Jan 2026 07:28:04 +0000
Received: from dfw.mirrors.kernel.org ([142.0.200.124])
	by witcher.mxrouting.net with esmtps  (TLS1.3) tls TLS_AES_256_GCM_SHA384
	(Exim 4.98)
	(envelope-from <stable+bounces-210709-hi=josie.lol@vger.kernel.org>)
	id 1viSdI-0000000Bli7-0PUL
	for hi@josie.lol;
	Wed, 21 Jan 2026 07:28:04 +0000
Received: from smtp.subspace.kernel.org (relay.kernel.org [52.25.139.140])
	(using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by dfw.mirrors.kernel.org (Postfix) with ESMTPS id ED75A6C2F96
	for <hi@josie.lol>; Wed, 21 Jan 2026 07:26:42 +0000 (UTC)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.subspace.kernel.org (Postfix) with ESMTP id 81EB43D6679;
	Wed, 21 Jan 2026 07:26:40 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="GvfZ23L2"
X-Original-To: stable@vger.kernel.org
Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id E3D9F1DF987;
	Wed, 21 Jan 2026 07:26:39 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1768980400; cv=none; b=H4kNoDwCqXXpbptHS2+POZlABOw6zOWoXNur8hT61H/K5s4FobCeC3hSSp26EDxDVrfzL2JgcCjeRnB07RHrRhXA2+cGskAtnyR0E27eNPNx4JFvm7sDRgZCCMktgl7LIepoPeEkB9HqySsFfP3fKMZ+ekP06pC+EBtYMAuQwos=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1768980400; c=relaxed/simple;
	bh=yEy8ny2OHjOtoQ2ahukebTc7/PIRqGKPRC4eM81ckRg=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=Pontqo1T4LHLA9iUchLbrgqH2xTkTZcaW1fDxxgygWBT+jM6i3Ta8eIWq5dp/LIGIA9ygsl9tbYTZaQXLrBpR8hj0mSrF+MjSEdF11cl9NaGTd+N6H4GklVruGHOAbE+1wUh5VALNeT/u5kwrS06XzB86lASuZhh3sRbCBZklMU=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=GvfZ23L2; arc=none smtp.client-ip=10.30.226.201
Received: by smtp.kernel.org (Postfix) with ESMTPSA id C5DBAC116D0;
	Wed, 21 Jan 2026 07:26:38 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org;
	s=korg; t=1768980399;
	bh=yEy8ny2OHjOtoQ2ahukebTc7/PIRqGKPRC4eM81ckRg=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=GvfZ23L2UM5yHQfLC62glIikpstrcLJ2GYd9DbdSLzKHXYZsANEikxg7d9zeeDZYB
	 1pULdccyQ+ciRwBYKAZITQvI3Dhb4k7UPria7PIWAUV7zxNydQsu1c3NktSaZ90xYh
	 ewjxJfI/lPeA1cRIMrJftasv1CK4235VRkyrVg+A=
Date: Wed, 21 Jan 2026 08:26:36 +0100
From: Greg KH <gregkh@linuxfoundation.org>
To: Baolu Lu <baolu.lu@linux.intel.com>
Cc: Mario Limonciello <superm1@kernel.org>,
	Mario Limonciello <mario.limonciello@amd.com>,
	regressions <regressions@lists.linux.dev>, stable@vger.kernel.org,
	iommu@lists.linux.dev, "Hegde, Vasant" <Vasant.Hegde@amd.com>,
	"Hou, Lizhi" <lizhi.hou@amd.com>
Subject: Re: IOMMU regression in linux-6.18.y
Message-ID: <2026012112-phantom-music-f6e8@gregkh>
References: <870872aa-28e9-412a-bac6-8020bf560e4f@amd.com>
 <c51ed4bf-ec2a-45f1-a077-8e2236076827@kernel.org>
 <3fccd233-c5cf-4252-98ea-61f240f82695@linux.intel.com>
Precedence: bulk
X-Mailing-List: stable@vger.kernel.org
List-Id: <stable.vger.kernel.org>
List-Subscribe: <mailto:stable+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:stable+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3fccd233-c5cf-4252-98ea-61f240f82695@linux.intel.com>
SPFCheck: Soft Fail, 20 Spam score
X-DKIM: signer='linuxfoundation.org' status='pass' reason=''
DKIMCheck: Server passes DKIM test, 0 Spam score
X-Spam-Score: 0.3 (/)
X-Spam-Report: Spam detection software, running on the system "witcher.mxrouting.net", has
 performed the tests listed below against this email.
 Information: https://mxroutedocs.com/directadmin/spamfilters/
 ---
 Content analysis details:   (0.3 points)
 ---
  pts rule name              description
 ---- ---------------------- -----------------------------------------
  0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was
                             blocked.  See
                             http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                              for more information.
                             [URIs: linuxfoundation.org]
  1.5 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level
                             mail domains are different
 -0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
  0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily
                             valid
 -0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from
                             author's domain
 -1.0 MAILING_LIST_MULTI     Multiple indicators imply a widely-seen list
                             manager
 -0.1 DKIMWL_WL_HIGH         DKIMwl.org - High trust sender
SpamTally: Final spam score: 23

On Wed, Jan 21, 2026 at 03:14:42PM +0800, Baolu Lu wrote:
> On 1/21/26 13:26, Mario Limonciello wrote:
> > 
> > 
> > On 1/20/26 8:08 PM, Mario Limonciello wrote:
> > > Hi,
> > > 
> > > Recently I found out that amdxdna stopped working in linux-6.18.4.
> > > This is because of this commit in linux-6.18.y:
> > > 
> > > commit c341dee80b5d ("iommu: disable SVA when CONFIG_X86 is set")
> > > 
> > > That was originally backported from upstream:
> > > 
> > > commit 72f98ef9a4be ("iommu: disable SVA when CONFIG_X86 is set")
> > > 
> > > ---
> > > 
> > > SVA support is a requirement for amdxdna.
> > > 
> > > The series that this commit came from was part of a larger 8 patch
> > > series, but this was the only commit that was CC'ed to stable.
> > > 
> > > As a result this is not broken in 6.19-rc, but it is broken in
> > > linux-6.18.y (and presumably any older stable kernels still around
> > > that picked it up).
> > > 
> > > So there are two options I see:
> > > 
> > > 1) Revert c341dee80b5d in linux-6.18.y (and any other stable kernel
> > > that picked it up but has amdxdna)
> > > 
> > > 2) Bring the entire 8 patch series to linux-6.18.y.
> > > 
> > > This is the entire series (I didn't look up the hashes from
> > > mainline, but they should have all landed):
> > > https://lore.kernel.org/linux-iommu/20251022082635.2462433-1-
> > > baolu.lu@linux.intel.com/
> > > 
> > > What should we do?
> > > 
> > 
> > If the decision is to take the remaining commits to 6.18.y to fix this I
> > did confirm they cleanly cherry pick and build.  Here are the hashes.
> > 
> > commit 27bfafac65d8 ("mm: add a ptdesc flag to mark kernel page tables")
> > commit 977870522af3 ("mm: actually mark kernel page table pages")
> > commit 412d000346ea ("x86/mm: use 'ptdesc' when freeing PMD pages")
> > commit 018942956723 ("mm: introduce pure page table freeing function")
> > commit bf9e4e30f353 ("x86/mm: use pagetable_free()")
> > commit 5ba2f0a15564 ("mm: introduce deferred freeing for kernel page
> > tables")
> > commit e37d5a2d60a3 ("iommu/sva: invalidate stale IOTLB entries for
> > kernel address space")
> > 
> 
> Yes. These patches fix a security issue in iommu/sva on x86 and restore
> the SVA functionality.

So all should be backported?  If so, great, but why were they not tagged
as such?

thanks,

greg k-h


From - Wed Jan 21 07:33:40 2026
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Return-Path: <stable+bounces-210710-hi=josie.lol@vger.kernel.org>
Delivered-To: hi@josie.lol
Received: from witcher.mxrouting.net
	by witcher.mxrouting.net with LMTP
	id aDciDE+BcGktUygAYBR5ng
	(envelope-from <stable+bounces-210710-hi=josie.lol@vger.kernel.org>)
	for <hi@josie.lol>; Wed, 21 Jan 2026 07:33:35 +0000
Return-path: <stable+bounces-210710-hi=josie.lol@vger.kernel.org>
Envelope-to: hi@josie.lol
Delivery-date: Wed, 21 Jan 2026 07:33:35 +0000
Received: from dfw.mirrors.kernel.org ([142.0.200.124])
	by witcher.mxrouting.net with esmtps  (TLS1.3) tls TLS_AES_256_GCM_SHA384
	(Exim 4.98)
	(envelope-from <stable+bounces-210710-hi=josie.lol@vger.kernel.org>)
	id 1viSic-0000000BwZn-2jK8
	for hi@josie.lol;
	Wed, 21 Jan 2026 07:33:35 +0000
Received: from smtp.subspace.kernel.org (relay.kernel.org [52.25.139.140])
	(using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by dfw.mirrors.kernel.org (Postfix) with ESMTPS id 3FCAE50839F
	for <hi@josie.lol>; Wed, 21 Jan 2026 07:33:05 +0000 (UTC)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.subspace.kernel.org (Postfix) with ESMTP id 6831843CEC1;
	Wed, 21 Jan 2026 07:33:00 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (