[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1164349c-93a5-ebb8-94aa-dbe03957c40f@gmail.com>
Date: Thu, 9 Dec 2021 06:50:43 -0800
From: James Smart <jsmart2021@...il.com>
To: Kees Cook <keescook@...omium.org>,
James Smart <james.smart@...adcom.com>
Cc: Dick Kennedy <dick.kennedy@...adcom.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH] scsi: lpfc: Use struct_group() to initialize struct
lpfc_cgn_info
On 12/8/2021 11:59 AM, Kees Cook wrote:
> In preparation for FORTIFY_SOURCE performing compile-time and run-time
> field bounds checking for memset(), avoid intentionally writing across
> neighboring fields.
>
> Add struct_group() to mark "stat" region of struct lpfc_cgn_info that
> should be initialized to zero, and refactor the "data" region memset()
> to wipe everything up to the cgn_stats region.
>
> Signed-off-by: Kees Cook <keescook@...omium.org>
> ---
looks fine.
Reviewed-by: James Smart <jsmart2021@...il.com>
-- james
Powered by blists - more mailing lists