From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Shen Lichuan <shenlichuan@vivo.com>
Cc: mitr@volny.cz, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] Input: wistron_btns - use kmemdup_array instead of kmemdup for multiple allocation
Date: Mon, 26 Aug 2024 10:25:46 -0700 [thread overview]
Message-ID: <Zsy6mvOkn7PkrUuv@google.com> (raw)
In-Reply-To: <20240826045253.3503-1-shenlichuan@vivo.com>
On Mon, Aug 26, 2024 at 12:52:53PM +0800, Shen Lichuan wrote:
> Let the kmemdup_array() take care about multiplication
> and possible overflows.
>
> Using kmemdup_array() is more appropriate and makes the code
> easier to audit.
>
> Signed-off-by: Shen Lichuan <shenlichuan@vivo.com>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2024-08-26 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 4:52 [PATCH v1] Input: wistron_btns - use kmemdup_array instead of kmemdup for multiple allocation Shen Lichuan
2024-08-26 17:25 ` Dmitry Torokhov [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=Zsy6mvOkn7PkrUuv@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitr@volny.cz \
--cc=shenlichuan@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).