From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Kees Cook <keescook@chromium.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Don Brace <don.brace@microchip.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
storagedev@microchip.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v3][next] scsi: smartpqi: Replace one-element array with flexible-array member
Date: Tue, 7 Feb 2023 17:09:06 -0600 [thread overview]
Message-ID: <22599902-57bb-a137-047e-867f35b45b69@embeddedor.com> (raw)
In-Reply-To: <63e2d840.170a0220.2b199.00a7@mx.google.com>
On 2/7/23 17:01, Kees Cook wrote:
> On Tue, Feb 07, 2023 at 03:59:43PM -0600, Gustavo A. R. Silva wrote:
>> One-element arrays are deprecated, and we are replacing them with flexible
>> array members instead. So, replace one-element array with flexible-array
>> member in struct report_log_lun_list.
>>
>> This helps with the ongoing efforts to tighten the FORTIFY_SOURCE routines
>> on memcpy().
>>
>> Link: https://github.com/KSPP/linux/issues/79
>> Link: https://github.com/KSPP/linux/issues/204
>> Acked-by: Don Brace <don.brace@microchip.com>
>> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
>
> Looks good to me -- both before and after, there is 1 extra all-zero
> entry at the end. But now the struct is using a flex array correctly.
Yep. :)
>
> Reviewed-by: Kees Cook <keescook@chromium.org>
Thanks!
--
Gustavo
>
> -Kees
>
>> ---
>> Changes in v3:
>> - Amplify the existing comment instead of adding a new one. By Don
>> Brace[1].
>> - Add Don's Acked-by tag to the changelog.
>> Link: https://lore.kernel.org/linux-hardening/d881ad98-a291-1c9b-53dc-199f23f1625e@embeddedor.com/ [1]
>>
>> Changes in v2:
>> - In v1 we thought that the original code was allocating one too-many
>> entries for the list. However, Don Brace commented that the allocation
>> was actually intentional[2]. So, I added a code comment with his feedback.
>> Link: https://lore.kernel.org/linux-hardening/16e6c434-44af-2efb-d4bc-a253e93e5590@embeddedor.com/ [2]
>>
>> v1:
>> - Link: https://lore.kernel.org/linux-hardening/c80c0979933e0c05e80d95792ef167a28640a14b.1663816572.git.gustavoars@kernel.org/
>>
>> drivers/scsi/smartpqi/smartpqi.h | 2 +-
>> drivers/scsi/smartpqi/smartpqi_init.c | 3 ++-
>> 2 files changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/scsi/smartpqi/smartpqi.h b/drivers/scsi/smartpqi/smartpqi.h
>> index af27bb0f3133..228838eb3686 100644
>> --- a/drivers/scsi/smartpqi/smartpqi.h
>> +++ b/drivers/scsi/smartpqi/smartpqi.h
>> @@ -954,7 +954,7 @@ struct report_log_lun {
>>
>> struct report_log_lun_list {
>> struct report_lun_header header;
>> - struct report_log_lun lun_entries[1];
>> + struct report_log_lun lun_entries[];
>> };
>>
>> struct report_phys_lun_8byte_wwid {
>> diff --git a/drivers/scsi/smartpqi/smartpqi_init.c b/drivers/scsi/smartpqi/smartpqi_init.c
>> index d0446d4d4465..49a8f91810b6 100644
>> --- a/drivers/scsi/smartpqi/smartpqi_init.c
>> +++ b/drivers/scsi/smartpqi/smartpqi_init.c
>> @@ -1259,7 +1259,8 @@ static int pqi_get_device_lists(struct pqi_ctrl_info *ctrl_info,
>> "report logical LUNs failed\n");
>>
>> /*
>> - * Tack the controller itself onto the end of the logical device list.
>> + * Tack the controller itself onto the end of the logical device list
>> + * by adding a list entry that is all zeros.
>> */
>>
>> logdev_data = *logdev_list;
>> --
>> 2.34.1
>>
>
next prev parent reply other threads:[~2023-02-07 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 21:59 Gustavo A. R. Silva
2023-02-07 23:01 ` Kees Cook
2023-02-07 23:09 ` Gustavo A. R. Silva [this message]
2023-02-09 0:04 ` Martin K. Petersen
2023-02-14 16:57 ` Martin K. Petersen
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=22599902-57bb-a137-047e-867f35b45b69@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=don.brace@microchip.com \
--cc=gustavoars@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=storagedev@microchip.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
Powered by JetHome