From: syzbot <syzbot+d60be66dd00b4490fa96@syzkaller.appspotmail.com>
To: kartikey406@gmail.com
Cc: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH v2] RDMA/uverbs: Free all radix tree nodes in uverbs_destroy_api()
Date: Sun, 15 Nov 2026 06:24:58 -0800 [thread overview]
Message-ID: <6af9c0ba.920b2b3a.148c65.0027.GAE@google.com> (raw)
In-Reply-To: <20261115142448.21160-1-kartikey406@gmail.com>
> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
Patch testing via #syz test is temporarily disabled.
See https://github.com/google/syzkaller/issues/8122 for details.
>
>
> syzbot reported a memory leak of radix_tree_node objects allocated
> while registering a siw device:
>
> radix_tree_node_alloc+0x81/0x1a0 lib/radix-tree.c:276
> radix_tree_insert+0x140/0x390 lib/radix-tree.c:712
> uapi_add_elm+0x61/0x140 uverbs_uapi.c:41
> uverbs_alloc_api+0x85/0xc50 uverbs_uapi.c:659
> siw_newlink+0x36a/0x3f0 siw_main.c:433
>
> radix_tree_insert() can fail with -ENOMEM after it has already linked
> intermediate nodes into the tree, leaving them with no entries.
> uverbs_destroy_api() only removes populated slots through
> uapi_remove_range(), and radix tree nodes are freed only as a side
> effect of deleting an entry, so these empty nodes are leaked when the
> uapi is destroyed.
>
> Call xa_destroy() after removing the entries so that all remaining
> nodes are freed.
>
> Reported-by: syzbot+d60be66dd00b4490fa96@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=d60be66dd00b4490fa96
> Fixes: 9ed3e5f44772 ("IB/uverbs: Build the specs into a radix tree at runtime")
> Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
> ---
> Changes in v2:
> - Drop the dummy insert/delete workaround in uapi_add_elm()
> - Call xa_destroy() in uverbs_destroy_api() to free all remaining
> nodes, as suggested by Jason
> ---
> drivers/infiniband/core/uverbs_uapi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/infiniband/core/uverbs_uapi.c b/drivers/infiniband/core/uverbs_uapi.c
> index b67db3790f03..77a4eb494936 100644
> --- a/drivers/infiniband/core/uverbs_uapi.c
> +++ b/drivers/infiniband/core/uverbs_uapi.c
> @@ -621,6 +621,7 @@ void uverbs_destroy_api(struct uverbs_api *uapi)
> return;
>
> uapi_remove_range(uapi, 0, U32_MAX);
> + xa_destroy(&uapi->radix);
> kfree(uapi->write_methods);
> kfree(uapi);
> }
> --
> 2.43.0
>
next parent reply other threads:[~2026-11-15 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261115142448.21160-1-kartikey406@gmail.com>
2026-11-15 14:24 ` syzbot [this message]
2026-11-15 14:29 [PATCH v2] RDMA/uverbs: Free all radix tree nodes in uverbs_destroy_api() Deepanshu Kartikey
2026-11-15 14:33 ` sashiko-bot
[not found] <20261115142356.21127-1-kartikey406@gmail.com>
2026-11-15 14:24 ` syzbot
[not found] <20261115141930.20935-1-kartikey406@gmail.com>
2026-11-15 14:19 ` syzbot
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=6af9c0ba.920b2b3a.148c65.0027.GAE@google.com \
--to=syzbot+d60be66dd00b4490fa96@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.