From: Kalle Valo <kvalo@kernel.org>
To: Yu Jiaoliang <yujiaoliang@vivo.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, opensource.kernel@vivo.com
Subject: Re: [PATCH v2] wifi: cfg80211: Use kmemdup_array instead of kmemdup for multiple allocation
Date: Wed, 21 Aug 2024 20:26:38 +0300 [thread overview]
Message-ID: <87a5h5hjn5.fsf@kernel.org> (raw)
In-Reply-To: <20240821111250.591558-1-yujiaoliang@vivo.com> (Yu Jiaoliang's message of "Wed, 21 Aug 2024 19:12:50 +0800")
Yu Jiaoliang <yujiaoliang@vivo.com> writes:
> Let the kememdup_array() take care about multiplication and possible
> overflows.
>
> v2:
> -Change sizeof(limits[0]) to sizeof(*limits)
> -Fix title prefix
>
> Signed-off-by: Yu Jiaoliang <yujiaoliang@vivo.com>
> Reviewed-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> Reviewed-by: Kalle Valo <kvalo@kernel.org>
No, I did not review your patch. Do not add any tags (like Reviewed-by)
unless a person gives you that in a reply.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-08-21 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 11:12 [PATCH v2] wifi: cfg80211: Use kmemdup_array instead of kmemdup for multiple allocation Yu Jiaoliang
2024-08-21 12:08 ` Christophe JAILLET
2024-08-21 17:26 ` Kalle Valo [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=87a5h5hjn5.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=pabeni@redhat.com \
--cc=yujiaoliang@vivo.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;
as well as URLs for NNTP newsgroup(s).