From: Will Deacon <will@kernel.org>
To: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Shameer Kolothum <skolothumtho@nvidia.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
nicolinc@nvidia.com, jgg@ziepe.ca, joro@8bytes.org,
robin.murphy@arm.com, nathanc@nvidia.com, mochs@nvidia.com
Subject: Re: [PATCH v3 0/2] iommu/arm-smmu-v3: Fix Tegra241 CMDQV CMD_SYNC use-after-free
Date: Wed, 22 Jul 2026 22:39:32 +0100 [thread overview]
Message-ID: <178472672974.2884042.6708017212584302884.b4-ty@kernel.org> (raw)
In-Reply-To: <20260629094106.251694-1-skolothumtho@nvidia.com>
On Mon, 29 Jun 2026 10:41:04 +0100, Shameer Kolothum wrote:
> Changes from v2:
> https://lore.kernel.org/linux-iommu/20260611084205.686559-1-skolothumtho@nvidia.com/
>
> -Addressed feedback and picked up R-by tags(Thanks!).
> -Use explicit type casts in devm action callbacks(patch #1)
> -Add Cc: stable to patch #1 as it is a pre requisite for patch #2.
>
> [...]
Applied to iommu (arm/smmu/updates), thanks!
[1/2] iommu/arm-smmu-v3: Manage teardown with devm
https://git.kernel.org/iommu/c/2bd22a0d4050
[2/2] iommu/tegra241-cmdqv: Fix CMD_SYNC use-after-free on teardown
https://git.kernel.org/iommu/c/9ff145a25c5c
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-07-22 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 9:41 Shameer Kolothum
2026-06-29 9:41 ` [PATCH v3 1/2] iommu/arm-smmu-v3: Manage teardown with devm Shameer Kolothum
2026-07-10 17:00 ` Jason Gunthorpe
2026-06-29 9:41 ` [PATCH v3 2/2] iommu/tegra241-cmdqv: Fix CMD_SYNC use-after-free on teardown Shameer Kolothum
2026-07-10 17:01 ` Jason Gunthorpe
2026-07-22 21:39 ` Will Deacon [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=178472672974.2884042.6708017212584302884.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochs@nvidia.com \
--cc=nathanc@nvidia.com \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=skolothumtho@nvidia.com \
/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
all inboxes | Powered by JetHome®