From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: markus.elfring@web.de, Thorsten Blum <thorsten.blum@toblux.com>
Cc: Shyam-sundar.S-k@amd.com, hdegoede@redhat.com,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86/amd/pmf: Use memdup_user()
Date: Mon, 27 May 2024 13:15:18 +0300 [thread overview]
Message-ID: <171680491830.2175.13318371328377311135.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20240527083628.210491-2-thorsten.blum@toblux.com>
On Mon, 27 May 2024 10:36:29 +0200, Thorsten Blum wrote:
> Switch to memdup_user() to overwrite the allocated memory only once
> instead of initializing the allocated memory to zero with kzalloc() and
> then immediately overwriting it with copy_from_user().
>
> Fix the following Coccinelle/coccicheck warning reported by
> memdup_user.cocci:
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo branch. Note it will show up in the public
platform-drivers-x86/review-ilpo branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/1] platform/x86/amd/pmf: Use memdup_user()
commit: 46de513068f956b76d68d241a7ad6bc5576d2948
--
i.
next prev parent reply other threads:[~2024-05-27 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 9:46 [PATCH] " Thorsten Blum
2024-05-10 11:12 ` Markus Elfring
2024-05-27 8:36 ` [PATCH v2] " Thorsten Blum
2024-05-27 10:15 ` Ilpo Järvinen [this message]
2024-05-27 10:38 ` Dan Carpenter
2024-05-30 14:15 ` Thorsten Blum
2024-05-30 19:28 ` Dan Carpenter
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=171680491830.2175.13318371328377311135.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hdegoede@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.elfring@web.de \
--cc=platform-driver-x86@vger.kernel.org \
--cc=thorsten.blum@toblux.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®