From: Yishai Hadas <yishaih@nvidia.com>
To: Prathamesh Deshpande <prathameshdeshpande7@gmail.com>,
<jgg@ziepe.ca>, <leon@kernel.org>
Cc: <linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH rdma v1] RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference
Date: Tue, 28 Apr 2026 17:55:22 +0300 [thread overview]
Message-ID: <4cdbb076-59c8-4ed8-b182-2ec644fd97e8@nvidia.com> (raw)
In-Reply-To: <bc0fcb45-c3f6-44ba-9448-ce4a09fad49f@nvidia.com>
On 27/04/2026 15:16, Yishai Hadas wrote:
> On 25/04/2026 3:59, Prathamesh Deshpande wrote:
>> MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT() links event_sub into sub_list
>> before initializing the fields used by the shared error path.
>>
>> If eventfd_ctx_fdget() then fails, the unwind path dereferences
>> event_sub->ev_file in uverbs_uobject_put() and calls
>> subscribe_event_xa_dealloc() with event_sub->xa_key_level1 still unset.
>>
>> Also, if kzalloc_obj() for event_sub fails after
>> subscribe_event_xa_alloc() succeeds, the current iteration is not yet
>> tracked in sub_list, so the shared unwind path cannot undo the XA
>> allocation.
>>
>> Initialize the shared-unwind fields before linking event_sub into
>> sub_list and explicitly unwind the XA allocation on event_sub allocation
>> failure.
>>
>> Fixes: 759738537142 ("IB/mlx5: Enable subscription for device events
>> over DEVX")
>> Signed-off-by: Prathamesh Deshpande <prathameshdeshpande7@gmail.com>
>
> LGDM
> Reviewed-by: Yishai Hadas <yishaih@nvidia.com>
Prathamesh,
Please see the below [1] review note from sashiko on your patch, it
seems right to me.
Can you please come with V2 while addressing it ?
The below [2] chunks on top of your V1 with a proper/improved commit log
can be considered as a proper solution.
I would add in the commit log something as of that.
"subscribe_event_xa_alloc() created the XA entry exactly once (on the
first occurrence of KEY_A), so subscribe_event_xa_dealloc() must also be
called exactly once for it.
Enforcing that by adding a helper function named devx_key_in_sub_list()
and call subscribe_event_xa_dealloc() only once the last occurrence
being cleaned up."
[1]
https://sashiko.dev/#/patchset/20260425010107.19586-1-prathameshdeshpande7%40gmail.com
[2] diff --git a/drivers/infiniband/hw/mlx5/devx.c
b/drivers/infiniband/hw/mlx5/devx.c
index 3d1528b1c816..c2ae5a140471 100644
--- a/drivers/infiniband/hw/mlx5/devx.c
+++ b/drivers/infiniband/hw/mlx5/devx.c
@@ -1913,6 +1913,17 @@ static int
UVERBS_HANDLER(MLX5_IB_METHOD_DEVX_OBJ_ASYNC_QUERY)(
return err;
}
+static bool devx_key_in_sub_list(struct list_head *list, u32 key_level1)
+{
+ struct devx_event_subscription *s;
+
+ list_for_each_entry(s, list, event_list)
+ if (s->xa_key_level1 == key_level1)
+ return true;
+
+ return false;
+}
+
static void
subscribe_event_xa_dealloc(struct mlx5_devx_event_table *devx_event_table,
u32 key_level1,
@@ -2160,10 +2171,11 @@ static int
UVERBS_HANDLER(MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT)(
event_sub = kzalloc_obj(*event_sub);
if (!event_sub) {
- subscribe_event_xa_dealloc(devx_event_table,
- key_level1,
- obj,
- obj_id);
+ if (!devx_key_in_sub_list(&sub_list, key_level1))
+ subscribe_event_xa_dealloc(devx_event_table,
+ key_level1,
+ obj,
+ obj_id);
err = -ENOMEM;
goto err;
}
@@ -2228,10 +2240,11 @@ static int
UVERBS_HANDLER(MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT)(
list_for_each_entry_safe(event_sub, tmp_sub, &sub_list,
event_list) {
list_del(&event_sub->event_list);
- subscribe_event_xa_dealloc(devx_event_table,
- event_sub->xa_key_level1,
- obj,
- obj_id);
+ if (!devx_key_in_sub_list(&sub_list,
event_sub->xa_key_level1))
+ subscribe_event_xa_dealloc(devx_event_table,
+ event_sub->xa_key_level1,
+ obj,
+ obj_id);
if (event_sub->eventfd)
eventfd_ctx_put(event_sub->eventfd);
Yishai
>
>> ---
>> drivers/infiniband/hw/mlx5/devx.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/infiniband/hw/mlx5/devx.c b/drivers/infiniband/
>> hw/mlx5/devx.c
>> index 645ebcc0832d..3d1528b1c816 100644
>> --- a/drivers/infiniband/hw/mlx5/devx.c
>> +++ b/drivers/infiniband/hw/mlx5/devx.c
>> @@ -2160,10 +2160,16 @@ static int
>> UVERBS_HANDLER(MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT)(
>> event_sub = kzalloc_obj(*event_sub);
>> if (!event_sub) {
>> + subscribe_event_xa_dealloc(devx_event_table,
>> + key_level1,
>> + obj,
>> + obj_id);
>> err = -ENOMEM;
>> goto err;
>> }
>> + event_sub->ev_file = ev_file;
>> + event_sub->xa_key_level1 = key_level1;
>> list_add_tail(&event_sub->event_list, &sub_list);
>> uverbs_uobject_get(&ev_file->uobj);
>> if (use_eventfd) {
>> @@ -2178,9 +2184,6 @@ static int
>> UVERBS_HANDLER(MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT)(
>> }
>> event_sub->cookie = cookie;
>> - event_sub->ev_file = ev_file;
>> - /* May be needed upon cleanup the devx object/subscription */
>> - event_sub->xa_key_level1 = key_level1;
>> event_sub->xa_key_level2 = obj_id;
>> INIT_LIST_HEAD(&event_sub->obj_list);
>> }
>
next prev parent reply other threads:[~2026-04-28 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 0:59 [PATCH rdma v1] RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference Prathamesh Deshpande
2026-04-27 12:16 ` Yishai Hadas
2026-04-28 14:55 ` Yishai Hadas [this message]
2026-04-28 22:49 ` Prathamesh Deshpande
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=4cdbb076-59c8-4ed8-b182-2ec644fd97e8@nvidia.com \
--to=yishaih@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=prathameshdeshpande7@gmail.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