From: Joerg Roedel <joro@8bytes.org>
To: Zhen Ni <zhen.ni@easystack.cn>
Cc: suravee.suthikulpanit@amd.com, will@kernel.org,
robin.murphy@arm.com, iommu@lists.linux.dev,
stable@vger.kernel.org
Subject: Re: [PATCH] iommu/amd: Fix ivrs_base memleak in early_amd_iommu_init()
Date: Fri, 5 Sep 2025 14:42:25 +0200 [thread overview]
Message-ID: <aLrase4rA1Thk4Jy@8bytes.org> (raw)
In-Reply-To: <20250822024915.673427-1-zhen.ni@easystack.cn>
On Fri, Aug 22, 2025 at 10:49:15AM +0800, Zhen Ni wrote:
> Fix a permanent ACPI table memory leak in early_amd_iommu_init() when
> CMPXCHG16B feature is not supported
>
> Fixes: 82582f85ed22 ("iommu/amd: Disable AMD IOMMU if CMPXCHG16B feature is not supported")
> Cc: stable@vger.kernel.org
> Signed-off-by: Zhen Ni <zhen.ni@easystack.cn>
> ---
> drivers/iommu/amd/init.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Applied for -rc, thanks.
prev parent reply other threads:[~2025-09-05 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250822024915.673427-1-zhen.ni@easystack.cn>
2025-08-22 20:59 ` [PATCH] iommu/amd: Fix ivrs_base memleak in early_amd_iommu_init() Suthikulpanit, Suravee
2025-09-05 12:42 ` Joerg Roedel [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=aLrase4rA1Thk4Jy@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=will@kernel.org \
--cc=zhen.ni@easystack.cn \
/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