[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <170681081625.3764000.6431595387488802492.b4-ty@chromium.org>
Date: Thu, 1 Feb 2024 10:06:58 -0800
From: Kees Cook <keescook@...omium.org>
To: linux-hardening@...r.kernel.org,
error27@...il.com,
gustavoars@...nel.org,
Bryan Tan <bryantan@...are.com>,
Vishnu Dasa <vdasa@...are.com>,
VMware PV-Drivers Reviewers <pv-drivers@...are.com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org,
Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
Cc: Kees Cook <keescook@...omium.org>,
vegard.nossum@...cle.com,
darren.kenny@...cle.com
Subject: Re: [PATCH v2 1/2] VMCI: Use struct_size() in kmalloc()
On Fri, 05 Jan 2024 08:39:59 -0800, Harshit Mogalapalli wrote:
> Use struct_size() instead of open coding.
>
>
Applied to for-next/hardening, thanks!
[1/2] VMCI: Use struct_size() in kmalloc()
https://git.kernel.org/kees/c/e03d4910e6e4
[2/2] VMCI: Fix memcpy() run-time warning in dg_dispatch_as_host()
https://git.kernel.org/kees/c/19b070fefd0d
Take care,
--
Kees Cook
Powered by blists - more mailing lists