From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "idryomov@gmail.com" <idryomov@gmail.com>,
Xiubo Li <xiubli@redhat.com>,
"islituo@gmail.com" <islituo@gmail.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] net: ceph: make free_choose_arg_map() resilient to partial allocation
Date: Tue, 23 Dec 2025 23:01:31 +0000 [thread overview]
Message-ID: <dc95e2dbc1293fe00aea3518443a241b890eef79.camel@ibm.com> (raw)
In-Reply-To: <20251220181149.46699-1-islituo@gmail.com>
On Sun, 2025-12-21 at 02:11 +0800, Tuo Li wrote:
> free_choose_arg_map() may dereference a NULL pointer if its caller fails
> after a partial allocation.
>
> For example, in decode_choose_args(), if allocation of arg_map->args
> fails, execution jumps to the fail label and free_choose_arg_map() is
> called. Since arg_map->size is updated to a non-zero value before memory
> allocation, free_choose_arg_map() will iterate over arg_map->args and
> dereference a NULL pointer.
>
> To prevent this potential NULL pointer dereference and make
> free_choose_arg_map() more resilient, add checks for pointers before
> iterating.
>
> Signed-off-by: Tuo Li <islituo@gmail.com>
> ---
> v2:
> * Add pointer checks before iterating in free_choose_arg_map(), instead of
> moving the arg_map->size assignment in decode_choose_args().
> Thanks to Viacheslav Dubeyko for pointing out the issue with the previous
> patch, and to Ilya Dryomov for the helpful advice.
> ---
> net/ceph/osdmap.c | 20 ++++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/net/ceph/osdmap.c b/net/ceph/osdmap.c
> index 34b3ab59602f..08157945af43 100644
> --- a/net/ceph/osdmap.c
> +++ b/net/ceph/osdmap.c
> @@ -241,22 +241,26 @@ static struct crush_choose_arg_map *alloc_choose_arg_map(void)
>
> static void free_choose_arg_map(struct crush_choose_arg_map *arg_map)
> {
> - if (arg_map) {
> - int i, j;
> + int i, j;
> +
> + if (!arg_map)
> + return;
>
> - WARN_ON(!RB_EMPTY_NODE(&arg_map->node));
> + WARN_ON(!RB_EMPTY_NODE(&arg_map->node));
>
> + if (arg_map->args) {
> for (i = 0; i < arg_map->size; i++) {
> struct crush_choose_arg *arg = &arg_map->args[i];
> -
> - for (j = 0; j < arg->weight_set_size; j++)
> - kfree(arg->weight_set[j].weights);
> - kfree(arg->weight_set);
> + if (arg->weight_set) {
> + for (j = 0; j < arg->weight_set_size; j++)
> + kfree(arg->weight_set[j].weights);
> + kfree(arg->weight_set);
> + }
> kfree(arg->ids);
> }
> kfree(arg_map->args);
> - kfree(arg_map);
> }
> + kfree(arg_map);
> }
>
> DEFINE_RB_FUNCS(choose_arg_map, struct crush_choose_arg_map, choose_args_index,
Looks good. Thanks a lot for the fix.
Reviewed-by: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
Thanks,
Slava.
next prev parent reply other threads:[~2025-12-23 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 18:11 Tuo Li
2025-12-23 23:01 ` Viacheslav Dubeyko [this message]
2026-01-05 12:53 ` Ilya Dryomov
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=dc95e2dbc1293fe00aea3518443a241b890eef79.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=islituo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiubli@redhat.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
all inboxes | Powered by JetHome®