From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Kees Cook <keescook@chromium.org>
Cc: Sumit Saxena <sumit.saxena@broadcom.com>,
Himanshu Madhani <himanshu.madhani@oracle.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
kernel test robot <lkp@intel.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] scsi: mpi3mr: Replace 1-element array with flex-array
Date: Tue, 21 Feb 2023 19:47:23 -0500 [thread overview]
Message-ID: <yq1bklmr0fg.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230204183715.never.937-kees@kernel.org> (Kees Cook's message of "Sat, 4 Feb 2023 10:37:16 -0800")
Kees,
> Nothing else defined MPI3_NVME_ENCAP_CMD_MAX, so the "command" buffer
> was being defined as a fake flexible array of size 1. Replace this
> with a proper flex array. Avoids this GCC 13 warning under
> -fstrict-flex-arrays=3:
Applied to 6.3/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2023-02-22 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 18:37 [PATCH] scsi: mpi3mr: Replace 1-element array with flex-array Kees Cook
2023-02-22 0:47 ` Martin K. Petersen [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=yq1bklmr0fg.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=himanshu.madhani@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=sumit.saxena@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