From: srini@kernel.org
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org,
Kees Cook <kees+treewide@kernel.org>,
Srinivas Kandagatla <srini@kernel.org>
Subject: [PATCH 4/9] nvmem: core: Add const to pattrs allocation type
Date: Fri, 2 Oct 2026 11:13:47 +0100 [thread overview]
Message-ID: <20261002101352.1084447-5-srini@kernel.org> (raw)
In-Reply-To: <20261002101352.1084447-1-srini@kernel.org>
From: Kees Cook <kees+treewide@kernel.org>
In preparation for making the devm_kmalloc family of allocators type
aware, we need to make sure that the returned type from the allocation
matches the type of the variable being assigned. (Before, the allocator
would always return "void *", which can be implicitly cast to any
pointer type.)
The assigned type is "const struct bin_attribute **", but the converted
allocation type would be "struct bin_attribute **", which is the same
type without the const qualifier. As there is no general way to safely
add const qualifiers, take the size from the assignment target instead.
No change in allocation size results.
Build tested ARCH=x86_64 allmodconfig with GCC 16.2.0:
drivers/nvmem/core.o
Assisted-by: LLM coccinelle
Signed-off-by: Kees Cook <kees+treewide@kernel.org>
Signed-off-by: Srinivas Kandagatla <srini@kernel.org>
---
drivers/nvmem/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
index 0556d140170a..19edc9ab0282 100644
--- a/drivers/nvmem/core.c
+++ b/drivers/nvmem/core.c
@@ -485,7 +485,7 @@ static int nvmem_populate_sysfs_cells(struct nvmem_device *nvmem)
/* Allocate an array of attributes with a sentinel */
ncells = list_count_nodes(&nvmem->cells);
pattrs = devm_kcalloc(&nvmem->dev, ncells + 1,
- sizeof(struct bin_attribute *), GFP_KERNEL);
+ sizeof(*pattrs), GFP_KERNEL);
if (!pattrs)
return -ENOMEM;
--
2.53.0
next prev parent reply other threads:[~2026-10-02 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 10:13 [PATCH 0/9] nvmem: patches for 7.4 srini
2026-10-02 10:13 ` [PATCH 1/9] dt-bindings: nvmem: qfprom: Add compatible for Qualcomm Maili srini
2026-10-02 10:13 ` [PATCH 2/9] dt-bindings: nvmem: uniphier-efuse: Add ti,am62p-efuse compatible srini
2026-10-02 10:13 ` [PATCH 3/9] nvmem: uniphier-efuse: Enable for K3 SoCs srini
2026-10-02 10:13 ` srini [this message]
2026-10-02 10:13 ` [PATCH 5/9] nvmem: layouts: Support fixed-layout as the nvmem device node itself srini
2026-10-02 10:13 ` [PATCH 6/9] dt-bindings: mfd: mediatek: mt6397: add mt6323 PMIC EFUSE srini
2026-10-02 10:13 ` [PATCH 7/9] nvmem: add mt6323 PMIC EFUSE driver srini
2026-10-02 10:13 ` [PATCH 8/9] nvmem: remove duplicated reference counting srini
2026-10-02 10:13 ` [PATCH 9/9] nvmem: protect nvmem_device::ops with SRCU srini
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=20261002101352.1084447-5-srini@kernel.org \
--to=srini@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kees+treewide@kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®