From: Dan Carpenter <dan.carpenter@linaro.org>
To: sudeep.holla@arm.com
Cc: linux-arm-kernel@lists.infradead.org
Subject: [bug report] firmware: arm_ffa: Add schedule receiver callback mechanism
Date: Mon, 30 Oct 2023 17:31:04 +0300 [thread overview]
Message-ID: <0e8ddbca-d9da-4a3b-aae3-328993b62ba2@moroto.mountain> (raw)
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).
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.
1256 count, XA_PRESENT);
1257
1258 for (idx = 0; idx < count; idx++)
1259 kfree(info[idx]);
1260 kfree(info);
1261
1262 drv_info->partition_count = 0;
1263 xa_destroy(&drv_info->partition_info);
1264 }
regards,
dan carpenter
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-10-30 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 14:31 Dan Carpenter [this message]
2023-10-30 16:01 ` [bug report] firmware: arm_ffa: Add schedule receiver callback mechanism Sudeep Holla
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=0e8ddbca-d9da-4a3b-aae3-328993b62ba2@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sudeep.holla@arm.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