From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bodo Stroesser <bostroesser@gmail.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] uapi: target: Replace fake flex-array with flexible-array member
Date: Sun, 2 Apr 2023 22:15:04 -0400 [thread overview]
Message-ID: <168031383543.650124.8544574837401067751.b4-ty@oracle.com> (raw)
In-Reply-To: <ZBSchMvTdl7VObKI@work>
On Fri, 17 Mar 2023 10:59:48 -0600, Gustavo A. R. Silva wrote:
> Zero-length arrays as fake flexible arrays are deprecated and we are
> moving towards adopting C99 flexible-array members instead.
>
> Address the following warning found with GCC-13 and
> -fstrict-flex-arrays=3 enabled:
> CC drivers/target/target_core_user.o
> drivers/target/target_core_user.c: In function ‘queue_cmd_ring’:
> drivers/target/target_core_user.c:1096:15: warning: array subscript 0 is outside array bounds of ‘struct iovec[0]’ [-Warray-bounds=]
> 1096 | iov = &entry->req.iov[0];
> | ^~~~~~~~~~~~~~~~~~
> In file included from drivers/target/target_core_user.c:31:
> ./include/uapi/linux/target_core_user.h:122:38: note: while referencing ‘iov’
> 122 | struct iovec iov[0];
> | ^~~
>
> [...]
Applied to 6.4/scsi-queue, thanks!
[1/1] uapi: target: Replace fake flex-array with flexible-array member
https://git.kernel.org/mkp/scsi/c/5c8c74ef20e7
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2023-04-03 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 16:59 [PATCH][next] uapi: target: Replace fake flex-array with flexible-array member Gustavo A. R. Silva
2023-03-18 13:00 ` Bodo Stroesser
2023-03-20 18:33 ` Kees Cook
2023-03-24 20:59 ` Martin K. Petersen
2023-04-03 2:15 ` 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=168031383543.650124.8544574837401067751.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bostroesser@gmail.com \
--cc=gustavoars@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).