From: Vasant Hegde <vasant.hegde@amd.com>
To: "Jörg Rödel" <joro@8bytes.org>
Cc: iommu@lists.linux.dev, will@kernel.org, robin.murphy@arm.com,
suravee.suthikulpanit@amd.com,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
stable@vger.kernel.org, Joao Martins <joao.m.martins@oracle.com>
Subject: Re: [PATCH] iommu/amd/pgtbl: Fix possible race while increase page table level
Date: Sat, 13 Sep 2025 11:48:15 +0530 [thread overview]
Message-ID: <b167aa9e-efa3-4e3c-9fbc-13353737ef7c@amd.com> (raw)
In-Reply-To: <sizw3br3mzal4o5vej7njvnjxsd5ego37zw6ejsh5fufxdr36n@ubrpt7sxsn3d>
Joerg,
On 9/13/2025 11:40 AM, Jörg Rödel wrote:
> Hey Vasant,
>
> On Thu, Sep 11, 2025 at 12:14:15PM +0000, Vasant Hegde wrote:
>> Reported-by: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
>> Cc: stable@vger.kernel.org
>> Cc: Joao Martins <joao.m.martins@oracle.com>
>> Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
>> Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>
>
> Can you please send again with a Fixes tag?
I was not sure which commit I should pick for "Fixes" tag as this issue probably
exists since we introduce increase_address_space() but lot of things changed. So
I just Cced stable.
Looking into the git history, I think below commit is more appropriate. I will
update and resend the patch.
commit 754265bcab78a9014f0f99cd35e0d610fcd7dfa7
Author: Joerg Roedel <jroedel@suse.de>
Date: Fri Sep 6 10:39:54 2019 +0200
iommu/amd: Fix race in increase_address_space()
-Vasant
next prev parent reply other threads:[~2025-09-13 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 12:14 [PATCH] iommu/amd/pgtbl: Fix possible race while increase page table level Vasant Hegde
2025-09-13 6:10 ` Jörg Rödel
2025-09-13 6:18 ` Vasant Hegde [this message]
2025-09-18 14:17 ` Jason Gunthorpe
2025-09-22 10:05 ` Vasant Hegde
2025-09-22 13:02 ` Jason Gunthorpe
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=b167aa9e-efa3-4e3c-9fbc-13353737ef7c@amd.com \
--to=vasant.hegde@amd.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=iommu@lists.linux.dev \
--cc=joao.m.martins@oracle.com \
--cc=joro@8bytes.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