From: Mikulas Patocka <mpatocka@redhat.com>
To: Kees Cook <kees@kernel.org>
Cc: Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] dm: dm-zoned: Adjust dmz_load_mapping() allocation type
Date: Mon, 28 Apr 2025 12:49:53 +0200 (CEST) [thread overview]
Message-ID: <dc1191b4-1010-260b-b7cb-dc748a05e571@redhat.com> (raw)
In-Reply-To: <20250426061707.work.587-kees@kernel.org>
Hi
I accepted both patches.
Just nit-picking - I prefer type name as an argument to the sizeof
operator rather than variable name - because when someone needs to find
out where variables with a particular type are allocated, it can be easily
done with grep if the sizeof operator contains the type name. So I changed
your patches so that there are type names.
Mikulas
On Fri, 25 Apr 2025, Kees Cook wrote:
> In preparation for making the 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 "struct dmz_mblock **" but the returned type will
> be "struct dmz_mblk **". These are the same allocation size (pointer
> size), but the types do not match. Adjust the allocation type to match
> the assignment.
>
> Signed-off-by: Kees Cook <kees@kernel.org>
> ---
> Cc: Alasdair Kergon <agk@redhat.com>
> Cc: Mike Snitzer <snitzer@kernel.org>
> Cc: Mikulas Patocka <mpatocka@redhat.com>
> Cc: <dm-devel@lists.linux.dev>
> ---
> drivers/md/dm-zoned-metadata.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/md/dm-zoned-metadata.c b/drivers/md/dm-zoned-metadata.c
> index deff22ecccbb..8934ad20012c 100644
> --- a/drivers/md/dm-zoned-metadata.c
> +++ b/drivers/md/dm-zoned-metadata.c
> @@ -1687,7 +1687,7 @@ static int dmz_load_mapping(struct dmz_metadata *zmd)
>
> /* Metadata block array for the chunk mapping table */
> zmd->map_mblk = kcalloc(zmd->nr_map_blocks,
> - sizeof(struct dmz_mblk *), GFP_KERNEL);
> + sizeof(*zmd->map_mblk), GFP_KERNEL);
> if (!zmd->map_mblk)
> return -ENOMEM;
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-04-28 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 6:17 [PATCH] dm: dm-zoned: Adjust dmz_load_mapping() allocation type Kees Cook
2025-04-28 10:49 ` Mikulas Patocka [this message]
2026-02-05 4:08 ` Kees Cook
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=dc1191b4-1010-260b-b7cb-dc748a05e571@redhat.com \
--to=mpatocka@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.