From: Jason Gunthorpe <jgg@ziepe.ca>
To: Will Deacon <will@kernel.org>
Cc: Peiyang He <peiyang_he@smail.nju.edu.cn>,
joro@8bytes.org, kevin.tian@intel.com, robin.murphy@arm.com,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
baolu.lu@linux.intel.com
Subject: Re: [PATCH v3 0/2] iommu/iommufd: Fix IOPF group ownership UAF
Date: Sun, 26 Jul 2026 13:15:16 -0300 [thread overview]
Message-ID: <amYylLjeAXTeqWVM@ziepe.ca> (raw)
In-Reply-To: <amYBCzc2dfH8A6Mo@willie-the-truck>
On Sun, Jul 26, 2026 at 01:43:55PM +0100, Will Deacon wrote:
> On Mon, Jul 20, 2026 at 04:50:15PM +0800, Peiyang He wrote:
> > This series fixes a UAF caused by an IOPF group being owned both by the
> > generic pending list and IOMMUFD's userspace fault queues:
> >
> > 1/2 Minimum fix: dequeue accepted groups before IOMMUFD queues them
> > for userspace response, then remove the check on list_empty()
> > in iopf_group_response().
> >
> > 2/2 Refactor: make iopf_group_response() free the group as well
> > after responding.
> >
> > Changes in v3:
> > - split the v2 patch into a minimum UAF fix and a follow-up cleanup
> > (suggested by Kevin)
>
> Oops, I lost track of this as all the versions of the patches are in the
> same thread. Please try to avoid that, as it makes it hard to track in
> an email client and can also confuse tools such as b4.
>
> Anyway, it looks like v3 is ready to go. Jason, is this something you
> are planning to pick up or shall we take it via the IOMMU tree? It looks
> like patch 1 should go in for -rc.
Yeah I have a bunch of iommufd thing for rc I'l pick it
Thanks,
Jason
next prev parent reply other threads:[~2026-07-26 16:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 6:12 [BUG] iommu: KASAN slab-use-after-free in iommufd_auto_response_faults Peiyang He
2026-07-07 10:36 ` Peiyang He
2026-07-08 14:38 ` Ankit Soni
2026-07-13 6:10 ` Tian, Kevin
2026-07-13 9:01 ` Peiyang He
2026-07-15 4:24 ` [PATCH] iommu/iommufd: Fix IOPF group ownership UAF Peiyang He
2026-07-17 8:00 ` Tian, Kevin
2026-07-18 4:55 ` Peiyang He
2026-07-18 4:32 ` [PATCH v2] " Peiyang He
2026-07-20 5:13 ` Tian, Kevin
2026-07-20 8:50 ` [PATCH v3 0/2] " Peiyang He
2026-07-26 12:43 ` Will Deacon
2026-07-26 16:15 ` Jason Gunthorpe [this message]
[not found] ` <20260720085017.3998878-1-peiyang_he@smail.nju.edu.cn>
2026-07-20 8:50 ` [PATCH v3 1/2] " Peiyang He
2026-07-20 9:44 ` Tian, Kevin
2026-07-26 16:20 ` Jason Gunthorpe
2026-07-20 8:50 ` [PATCH v3 2/2] iommu: Make iopf_group_response() free groups Peiyang He
2026-07-20 9:44 ` Tian, Kevin
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=amYylLjeAXTeqWVM@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peiyang_he@smail.nju.edu.cn \
--cc=robin.murphy@arm.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