From: Kees Cook <keescook@chromium.org>
To: GUO Zihua <guozihua@huawei.com>
Cc: keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
davem@davemloft.net, dhowells@redhat.com,
herbert@gondor.apana.org.au, gustavoars@kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] crypto: Use struct_size() helper in kmalloc()
Date: Tue, 17 May 2022 14:26:44 -0700 [thread overview]
Message-ID: <202205171424.CF36CE58@keescook> (raw)
In-Reply-To: <20220517080532.31015-1-guozihua@huawei.com>
On Tue, May 17, 2022 at 04:05:32PM +0800, GUO Zihua wrote:
> Make use of struct_size() heler for structures containing flexible array
> member instead of sizeof() which prevents potential issues as well as
> addressing the following sparse warning:
>
> crypto/asymmetric_keys/asymmetric_type.c:155:23: warning: using sizeof
> on a flexible structure
> crypto/asymmetric_keys/asymmetric_type.c:247:28: warning: using sizeof
> on a flexible structure
>
> Reference: https://github.com/KSPP/linux/issues/174
>
> Signed-off-by: GUO Zihua <guozihua@huawei.com>
> ---
> crypto/asymmetric_keys/asymmetric_type.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/crypto/asymmetric_keys/asymmetric_type.c b/crypto/asymmetric_keys/asymmetric_type.c
> index 41a2f0eb4ce4..96a99a91bf17 100644
> --- a/crypto/asymmetric_keys/asymmetric_type.c
> +++ b/crypto/asymmetric_keys/asymmetric_type.c
> @@ -152,7 +152,7 @@ struct asymmetric_key_id *asymmetric_key_generate_id(const void *val_1,
> {
> struct asymmetric_key_id *kid;
>
> - kid = kmalloc(sizeof(struct asymmetric_key_id) + len_1 + len_2,
> + kid = kmalloc(struct_size(kid, data, len_1 + len_2),
Please use the size_add() helper for this open-coded add here.
> GFP_KERNEL);
> if (!kid)
> return ERR_PTR(-ENOMEM);
> @@ -244,7 +244,7 @@ struct asymmetric_key_id *asymmetric_key_hex_to_key_id(const char *id)
> if (asciihexlen & 1)
> return ERR_PTR(-EINVAL);
>
> - match_id = kmalloc(sizeof(struct asymmetric_key_id) + asciihexlen / 2,
> + match_id = kmalloc(struct_size(match_id, data, asciihexlen / 2),
There is no size_div(), but that's ok here because the denominator is an
constant expression.
> GFP_KERNEL);
> if (!match_id)
> return ERR_PTR(-ENOMEM);
> --
> 2.36.0
>
--
Kees Cook
next prev parent reply other threads:[~2022-05-17 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 8:05 [PATCH] crypto: Use struct_size() helper in kmalloc() GUO Zihua
2022-05-17 21:26 ` Kees Cook [this message]
2022-05-18 1:01 ` Guozihua (Scott)
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=202205171424.CF36CE58@keescook \
--to=keescook@chromium.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=guozihua@huawei.com \
--cc=gustavoars@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-hardening@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