From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
Kees Cook <keescook@chromium.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
regressions@lists.linux.dev
Subject: mainline build failure due to df8fc4e934c1 ("kbuild: Enable -fstrict-flex-arrays=3")
Date: Thu, 29 Jun 2023 14:53:39 +0100 [thread overview]
Message-ID: <ZJ2M4yqnOCqqGWH0@debian> (raw)
Hi All,
The latest mainline kernel branch fails to build with clang (version 16.0.1), and the errors are like:
drivers/scsi/aacraid/commsup.c:1170:17: error: array index 1 is past the end of the array (that has type 'u8[1]' (aka 'unsigned char[1]'), cast to '__le32 *' (aka 'unsigned int *')) [-Werror,-Warray-bounds]
(((__le32 *)aifcmd->data)[1] == cpu_to_le32(3));
^ ~
drivers/scsi/aacraid/aacraid.h:2621:2: note: array 'data' declared here
u8 data[1]; /* Undefined length (from kernel viewpoint) */
^
drivers/scsi/aacraid/commsup.c:1290:20: error: array index 3 is past the end of the array (that has type 'u8[1]' (aka 'unsigned char[1]'), cast to '__le32 *' (aka 'unsigned int *')) [-Werror,-Warray-bounds]
((((__le32 *)aifcmd->data)[3]
^
_______________________________________________________________________
drivers/staging/ks7010/ks_wlan_net.c:1600:34: error: array index 16 is past the end of the array (that has type '__u8[0]' (aka 'unsigned char[0]')) [-Werror,-Warray-bounds]
memcpy(&key->tx_mic_key[0], &enc->key[16], 8);
^ ~~
./include/linux/fortify-string.h:694:35: note: expanded from macro 'memcpy'
__struct_size(p), __struct_size(q), \
^
./include/linux/fortify-string.h:96:56: note: expanded from macro '__struct_size'
#define __struct_size(p) __builtin_dynamic_object_size(p, 0)
^
./include/linux/fortify-string.h:638:27: note: expanded from macro '__fortify_memcpy_chk'
const size_t __q_size = (q_size); \
^~~~~~
./include/uapi/linux/wireless.h:838:2: note: array 'key' declared here
__u8 key[0];
^
_______________________________________________________________________
git bisect pointed to df8fc4e934c1 ("kbuild: Enable -fstrict-flex-arrays=3").
Reverting the commit has fixed the build failure.
I will be happy to test any patch or provide any extra log if needed.
#regzbot introduced: df8fc4e934c12b906d08050d7779f292b9c5c6b5
--
Regards
Sudip
next reply other threads:[~2023-06-29 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 13:53 Sudip Mukherjee (Codethink) [this message]
2023-06-29 14:09 ` mainline build failure due to df8fc4e934c1 ("kbuild: Enable -fstrict-flex-arrays=3") Gustavo A. R. Silva
2023-07-07 12:52 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-07 16:17 ` Gustavo A. R. Silva
2023-07-07 16:31 ` Linux regression tracking (Thorsten Leemhuis)
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=ZJ2M4yqnOCqqGWH0@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.