From: Petr Pavlu <petr.pavlu@suse.com>
To: Kees Cook <kees@kernel.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Kees Cook <kees+treewide@kernel.org>,
Daniel Gomez <da.gomez@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Aaron Tomlin <atomlin@atomlin.com>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] modules/kmod: Allocate argv with kmalloc_array()
Date: Mon, 21 Sep 2026 13:55:15 +0200 [thread overview]
Message-ID: <d771ad48-9f75-4ca7-84c9-04139afbb7d4@suse.com> (raw)
In-Reply-To: <20260917211229.i.604-kees@kernel.org>
On 9/17/26 11:12 PM, Kees Cook wrote:
> From: Kees Cook <kees+treewide@kernel.org>
>
> In preparation for converting the kmalloc family of allocators to the
> type-aware kmalloc_obj family, we need to make sure that the returned
> type from the allocation matches the type of the variable being
> assigned. (The kmalloc family returns "void *", which can be implicitly
> cast to any pointer type.)
>
> argv holds 5 pointers, but the size was taken from the array type
> "char *[5]", which would make the allocation type a pointer to that
> array rather than the "char **" being assigned. Allocate 5 entries of
> the target's type instead. The resulting allocation size is the same.
>
> Build tested ARCH=x86_64 allmodconfig with GCC 16.2.0:
> kernel/module/kmod.o
>
> Assisted-by: LLM coccinelle
> Signed-off-by: Kees Cook <kees+treewide@kernel.org>
Looks ok to me. I've queued the patch on modules-next for 7.4-rc1.
--
Thanks,
Petr
prev parent reply other threads:[~2026-09-21 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 21:12 Kees Cook
2026-09-21 11:55 ` Petr Pavlu [this message]
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=d771ad48-9f75-4ca7-84c9-04139afbb7d4@suse.com \
--to=petr.pavlu@suse.com \
--cc=atomlin@atomlin.com \
--cc=da.gomez@kernel.org \
--cc=kees+treewide@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=samitolvanen@google.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®