public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [bug report] firmware: arm_ffa: Add schedule receiver callback mechanism
Date: Mon, 30 Oct 2023 16:01:07 +0000	[thread overview]
Message-ID: <ZT_TQ7bdCG6CjYqW@bogus> (raw)
In-Reply-To: <0e8ddbca-d9da-4a3b-aae3-328993b62ba2@moroto.mountain>

On Mon, Oct 30, 2023 at 05:31:04PM +0300, Dan Carpenter wrote:
> Hello Sudeep Holla,
> 
> The patch 0184450b8b1e: "firmware: arm_ffa: Add schedule receiver
> callback mechanism" from Oct 5, 2023 (linux-next), leads to the
> following Smatch static checker warning:
> 
> 	drivers/firmware/arm_ffa/driver.c:1251 ffa_partitions_cleanup()
> 	warn: double check that we're allocating correct size: 8 vs 88
> 
> drivers/firmware/arm_ffa/driver.c
>     1243 static void ffa_partitions_cleanup(void)
>     1244 {
>     1245         struct ffa_dev_part_info **info;
>     1246         int idx, count = drv_info->partition_count;
>     1247 
>     1248         if (!count)
>     1249                 return;
>     1250 
> --> 1251         info = kcalloc(count, sizeof(**info), GFP_KERNEL);
> 
> I *think* this should be sizeof(*info).  It ends up being a smaller
> allocation (8 bytes instead of 88).

Not sure if I am following this warning properly. I am bit confused whether
it suggest 8 is correct or 88 is correct. Anyways, the expectation is to
just allocate 8 bytes for a pointer. We just fetch a list of stored pointer
in XArray and free them.

One possible way to avoid any confusion is to use sizeof(struct ffa_dev_part_info *)
or even sizeof(void *).

> 
>     1252         if (!info)
>     1253                 return;
>     1254 
>     1255         xa_extract(&drv_info->partition_info, (void **)info, 0, VM_ID_MASK,
> 
> We copy count pointers to info.  We don't copy entire structs.  It still
> works but it's larger than necessary.
>

Yes, that is the expected behaviour. We copy the pointers that were allocated
in the setup and free them here.

-- 
Regards,
Sudeep

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-10-30 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 14:31 [bug report] firmware: arm_ffa: Add schedule receiver callback mechanism Dan Carpenter
2023-10-30 16:01 ` Sudeep Holla [this message]
2023-10-31  4:15   ` Dan Carpenter
2023-10-31  9:50     ` Sudeep Holla

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=ZT_TQ7bdCG6CjYqW@bogus \
    --to=sudeep.holla@arm.com \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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