Linux Hardening
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Kees Cook <keescook@chromium.org>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: James Bottomley <jejb@linux.ibm.com>,
	Sathya Prakash <sathya.prakash@broadcom.com>,
	Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
	Suganath Prabu Subramani  <suganath-prabu.subramani@broadcom.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	MPT-FusionLinux.pdl@broadcom.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2][next] scsi: mpt3sas: Replace one-element array with flexible-array in struct _MPI2_CONFIG_PAGE_IO_UNIT_3
Date: Wed, 10 Mar 2021 18:06:52 -0600	[thread overview]
Message-ID: <855e73f8-9b84-25b9-01e3-8ce368165b25@embeddedor.com> (raw)
In-Reply-To: <202103101058.16ED27BE3@keescook>



On 3/10/21 13:07, Kees Cook wrote:

>> diff --git a/drivers/scsi/mpt3sas/mpi/mpi2_cnfg.h b/drivers/scsi/mpt3sas/mpi/mpi2_cnfg.h
>> index 43a3bf8ff428..d00431f553e1 100644
>> --- a/drivers/scsi/mpt3sas/mpi/mpi2_cnfg.h
>> +++ b/drivers/scsi/mpt3sas/mpi/mpi2_cnfg.h
>> @@ -992,7 +992,7 @@ typedef struct _MPI2_CONFIG_PAGE_IO_UNIT_1 {
>>   *one and check the value returned for GPIOCount at runtime.
>>   */
>>  #ifndef MPI2_IO_UNIT_PAGE_3_GPIO_VAL_MAX
>> -#define MPI2_IO_UNIT_PAGE_3_GPIO_VAL_MAX    (1)
>> +#define MPI2_IO_UNIT_PAGE_3_GPIO_VAL_MAX    (36)
>>  #endif
>>
>>  typedef struct _MPI2_CONFIG_PAGE_IO_UNIT_3 {
>> diff --git a/drivers/scsi/mpt3sas/mpt3sas_ctl.c b/drivers/scsi/mpt3sas/mpt3sas_ctl.c
>> index 44f9a05db94e..23fcf29bfd67 100644
>> --- a/drivers/scsi/mpt3sas/mpt3sas_ctl.c
>> +++ b/drivers/scsi/mpt3sas/mpt3sas_ctl.c
>> @@ -3203,7 +3203,7 @@ BRM_status_show(struct device *cdev, struct device_attribute *attr,
>>  {
>>         struct Scsi_Host *shost = class_to_shost(cdev);
>>         struct MPT3SAS_ADAPTER *ioc = shost_priv(shost);
>> -       Mpi2IOUnitPage3_t *io_unit_pg3 = NULL;
>> +       Mpi2IOUnitPage3_t io_unit_pg3;
>>         Mpi2ConfigReply_t mpi_reply;
>>         u16 backup_rail_monitor_status = 0;
>>         u16 ioc_status;
>> @@ -3221,16 +3221,10 @@ BRM_status_show(struct device *cdev, struct device_attribute *attr,
>>                 goto out;
>>
>>         /* allocate upto GPIOVal 36 entries */
>> -       sz = offsetof(Mpi2IOUnitPage3_t, GPIOVal) + (sizeof(u16) * 36);
>> -       io_unit_pg3 = kzalloc(sz, GFP_KERNEL);
>> -       if (!io_unit_pg3) {
>> -               rc = -ENOMEM;
>> -               ioc_err(ioc, "%s: failed allocating memory for iounit_pg3: (%d) bytes\n",
>> -                       __func__, sz);
>> -               goto out;
>> -       }
>> +       sz = sizeof(io_unit_pg3);
>> +       memset(&io_unit_pg3, 0, sz);
> 
> I like this a lot. It makes the code way simpler.
> 
> Putting this on the stack makes it faster, and it's less than 100 bytes,
> which seems entirely reasonable.
> 
>>
>> -       if (mpt3sas_config_get_iounit_pg3(ioc, &mpi_reply, io_unit_pg3, sz) !=
>> +       if (mpt3sas_config_get_iounit_pg3(ioc, &mpi_reply, &io_unit_pg3, sz) !=
> 
> The only thing I can imagine is if this ends up doing DMA, which isn't
> allowed on the stack. However, in looking down through the call path,
> it's _copied_ into DMA memory, so this appears entirely safe.
>  
> Can you send this as a "normal" patch? Feel free to include:
> 
> Reviewed-by: Kees Cook <keescook@chromium.org>

Done: https://lore.kernel.org/lkml/20210310235951.GA108661@embeddedor/

Thanks for the comments!
--
Gustavo

      reply	other threads:[~2021-03-11  0:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 23:51 [PATCH v2][next] scsi: mpt3sas: Replace one-element array with flexible-array in struct _MPI2_CONFIG_PAGE_IO_UNIT_3 Gustavo A. R. Silva
2021-03-08 19:32 ` Gustavo A. R. Silva
2021-03-08 20:12   ` James Bottomley
2021-03-08 20:41     ` Gustavo A. R. Silva
2021-03-10 19:07       ` Kees Cook
2021-03-11  0:06         ` Gustavo A. R. Silva [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=855e73f8-9b84-25b9-01e3-8ce368165b25@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=MPT-FusionLinux.pdl@broadcom.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=sathya.prakash@broadcom.com \
    --cc=sreekanth.reddy@broadcom.com \
    --cc=suganath-prabu.subramani@broadcom.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