From: Joerg Roedel <joro@8bytes.org>
To: Pavel Paklov <Pavel.Paklov@cyberprotect.ru>
Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Wan Zongshun <Vincent.Wan@amd.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org, stable@vger.kernel.org
Subject: Re: [PATCH] iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid
Date: Thu, 17 Apr 2025 16:37:45 +0200 [thread overview]
Message-ID: <aAESOQ5xlTZewgo5@8bytes.org> (raw)
In-Reply-To: <20250325092259.392844-1-Pavel.Paklov@cyberprotect.ru>
On Tue, Mar 25, 2025 at 09:22:44AM +0000, Pavel Paklov wrote:
> Fixes: ca3bf5d47cec ("iommu/amd: Introduces ivrs_acpihid kernel parameter")
> Cc: stable@vger.kernel.org
> Signed-off-by: Pavel Paklov <Pavel.Paklov@cyberprotect.ru>
> ---
> drivers/iommu/amd/init.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
Applied for -rc, thanks.
prev parent reply other threads:[~2025-04-17 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 9:22 [PATCH] iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid Pavel Paklov
2025-04-17 14:37 ` 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=aAESOQ5xlTZewgo5@8bytes.org \
--to=joro@8bytes.org \
--cc=Pavel.Paklov@cyberprotect.ru \
--cc=Vincent.Wan@amd.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=will@kernel.org \
/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