From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@nvidia.com>
Cc: alex@shazbot.org, kvm@vkger.kernel.org,
"Leon Romanovsky" <leon@kernel.org>,
"Kevin Tian" <kevin.tian@intel.com>,
"Christian König" <christian.koenig@amd.com>,
"Carlos López" <clopez@suse.de>, "Matt Evans" <mattev@meta.com>,
"Joonas Kylmälä" <joonas.kylmala@netum.fi>,
stable@vger.kernel.org
Subject: Re: [PATCH] vfio/pci: fix dma-buf kref underflow after revoke
Date: Tue, 12 May 2026 10:44:42 -0300 [thread overview]
Message-ID: <20260512134442.GB7655@nvidia.com> (raw)
In-Reply-To: <20260507143548.1018405-1-alex.williamson@nvidia.com>
On Thu, May 07, 2026 at 08:35:46AM -0600, Alex Williamson wrote:
> vfio_pci_dma_buf_move(revoked=true) and vfio_pci_dma_buf_cleanup()
> ran the same drain sequence: set priv->revoked, invalidate mappings,
> wait for fences, drop the registered kref, wait for completion.
> When the VFIO device fd was closed after PCI_COMMAND_MEMORY had been
> cleared, both ran in turn -- the second kref_put underflowed and the
> subsequent wait_for_completion() blocked on a completion that the
> first run had already consumed:
>
> refcount_t: underflow; use-after-free.
> WARNING: lib/refcount.c:28 at refcount_warn_saturate+0x59/0x90
> Call Trace:
> vfio_pci_dma_buf_cleanup+0x163/0x168 [vfio_pci_core]
> vfio_pci_core_close_device+0x67/0xe0 [vfio_pci_core]
> vfio_df_close+0x4c/0x80 [vfio]
> vfio_df_group_close+0x36/0x80 [vfio]
> vfio_device_fops_release+0x21/0x40 [vfio]
> __fput+0xe6/0x2b0
> __x64_sys_close+0x3d/0x80
>
> Collapse the duplication: vfio_pci_dma_buf_cleanup() now delegates
> the drain to vfio_pci_dma_buf_move(true), which is idempotent for
> already-revoked dma-bufs. cleanup retains only list removal and
> the device registration drop; the dma_resv_lock that bracketed
> those is dropped along with the in-line drain that required it,
> memory_lock continues to protect them.
>
> Re-arm the kref and the completion at the end of move()'s revoke
> branch so post-revoke state matches post-creation (kref == 1,
> completion ready). This keeps cleanup's call into move() a no-op
> when revoke already ran, and replaces the explicit kref_init() that
> the un-revoke branch used to perform for the un-revoke -> remap
> path.
>
> Fixes: 1a8a5227f229 ("vfio: Wait for dma-buf invalidation to complete")
> Reported-by: Joonas Kylmälä <joonas.kylmala@netum.fi>
> Closes: https://lore.kernel.org/all/GVXPR02MB12019AA6014F27EF5D773E89BFB372@GVXPR02MB12019.eurprd02.prod.outlook.com/
> Cc: stable@vger.kernel.org
> Assisted-by: Claude:claude-opus-4-7
> Reviewed-by: Leon Romanovsky <leon@kernel.org>
> Signed-off-by: Alex Williamson <alex.williamson@nvidia.com>
> ---
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Jason
prev parent reply other threads:[~2026-05-12 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 14:35 [PATCH] vfio/pci: fix dma-buf kref underflow after revoke Alex Williamson
2026-05-08 8:18 ` Tian, Kevin
2026-05-12 13:44 ` Jason Gunthorpe [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=20260512134442.GB7655@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@nvidia.com \
--cc=alex@shazbot.org \
--cc=christian.koenig@amd.com \
--cc=clopez@suse.de \
--cc=joonas.kylmala@netum.fi \
--cc=kevin.tian@intel.com \
--cc=kvm@vkger.kernel.org \
--cc=leon@kernel.org \
--cc=mattev@meta.com \
--cc=stable@vger.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