From: "Kuehling, Felix" <felix.kuehling@amd.com>
To: "Henry Martin" <bsdhenrymartin@gmail.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Harry Wentland" <harry.wentland@amd.com>,
"Alex Hung" <alex.hung@amd.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] amdkfd: fix doorbell allocation race creating duplicate allocations
Date: Fri, 9 Oct 2026 11:00:33 -0400 [thread overview]
Message-ID: <2bbea75d-2e3f-4a57-a291-5f5d9ca698c5@amd.com> (raw)
In-Reply-To: <20261009101842.3294707-1-bsdhenrymartin@gmail.com>
On 2026-10-09 06:18, Henry Martin wrote:
> The check-and-allocate sequence on pdd->qpd.proc_doorbells is
> lockless at every call site of kfd_alloc_process_doorbells():
> kfd_get_process_doorbells() (mmap of /dev/kfd), kfd_ioctl_create_queue()
> and the CRIU restore path each test the pointer under different
> locking (or none), so two racing threads can both observe NULL and
> each allocate a doorbell BO and bitmap, orphaning one allocation and
> handing the two mappings different backing pages.
>
> Move the serialization into kfd_alloc_process_doorbells() itself:
> take kfd->doorbell_mutex and re-check under it, so all three call
> sites are covered regardless of their own locking. The existing
> doorbell_mutex users (kfd_get_kernel_doorbell() /
> kfd_release_kernel_doorbell()) only guard the device-global
> kfd->doorbell_bitmap in short non-sleeping sections and never call
> into this path, so there is no nesting.
>
> This vulnerability was discovered by Tencent CodeBuddy Security.
>
> Fixes: 428542d91772 ("drm/amd/display: Setup for mmhubbub3_warmup_mcif with big buffer")
> Signed-off-by: Henry Martin <bsdhenrymartin@gmail.com>
Reviewed-by: Felix Kuehling <felix.kuehling@amd.com>
I'm applying the patch to amd-staging-drm-next.
Thanks,
Felix
> ---
> drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c b/drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c
> index fdcf7f2d1b5b4..07f881573837e 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c
> @@ -257,12 +257,21 @@ int kfd_alloc_process_doorbells(struct kfd_dev *kfd, struct kfd_process_device *
> int r;
> struct qcm_process_device *qpd = &pdd->qpd;
>
> + mutex_lock(&kfd->doorbell_mutex);
> +
> + /* Another thread may have won the check-and-allocate race */
> + if (qpd->proc_doorbells) {
> + mutex_unlock(&kfd->doorbell_mutex);
> + return 0;
> + }
> +
> /* Allocate bitmap for dynamic doorbell allocation */
> qpd->doorbell_bitmap = bitmap_zalloc(KFD_MAX_NUM_OF_QUEUES_PER_PROCESS,
> GFP_KERNEL);
> if (!qpd->doorbell_bitmap) {
> DRM_ERROR("Failed to allocate process doorbell bitmap\n");
> - return -ENOMEM;
> + r = -ENOMEM;
> + goto unlock;
> }
>
> r = init_doorbell_bitmap(&pdd->qpd, kfd);
> @@ -284,11 +293,15 @@ int kfd_alloc_process_doorbells(struct kfd_dev *kfd, struct kfd_process_device *
> DRM_ERROR("Failed to allocate process doorbells\n");
> goto err;
> }
> +
> + mutex_unlock(&kfd->doorbell_mutex);
> return 0;
>
> err:
> bitmap_free(qpd->doorbell_bitmap);
> qpd->doorbell_bitmap = NULL;
> +unlock:
> + mutex_unlock(&kfd->doorbell_mutex);
> return r;
> }
>
> --
> 2.43.7
next prev parent reply other threads:[~2026-10-09 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 10:18 Henry Martin
2026-10-09 15:00 ` Kuehling, Felix [this message]
2026-10-09 15:33 ` Kuehling, Felix
2026-10-10 2:55 ` henry martin
2026-10-10 3:02 ` [PATCH v2] " Henry Martin
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=2bbea75d-2e3f-4a57-a291-5f5d9ca698c5@amd.com \
--to=felix.kuehling@amd.com \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bsdhenrymartin@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
/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®