From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>,
"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: Re: mainline build failure due to df8fc4e934c1 ("kbuild: Enable -fstrict-flex-arrays=3")
Date: Fri, 7 Jul 2023 14:52:28 +0200 [thread overview]
Message-ID: <423a78fe-ac40-9983-ff44-90b1759fc0b5@leemhuis.info> (raw)
In-Reply-To: <c0db4c48-6090-5c72-b597-9d4146dbc26c@embeddedor.com>
On 29.06.23 16:09, Gustavo A. R. Silva wrote:
>
> Thanks for the report. See my comments below.
Thx for your reply.
> On 6/29/23 07:53, Sudip Mukherjee (Codethink) wrote:
>>
>> 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));
>> ^ ~
> [...]
> These are addressed by this patch:
> https://lore.kernel.org/linux-hardening/65907ee4083de62fbaadc5c2e6512e3828912d1b.1687974498.git.gustavoars@kernel.org/
>
> in this series (for which I'll send v2 shortly):
> https://lore.kernel.org/linux-hardening/62386518-4123-db1f-4656-6b4ea509f5b1@embeddedor.com/T/
Are those fixes still on track? Looks like there was not much progress
since then, so I suspect this won't be fixed before -rc1? Or did miss
something?
Ciao, Thorsten
> [...]
>>
>> 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
>>
>>
>
>
next prev parent reply other threads:[~2023-07-07 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 13:53 mainline build failure due to df8fc4e934c1 ("kbuild: Enable -fstrict-flex-arrays=3") Sudip Mukherjee (Codethink)
2023-06-29 14:09 ` Gustavo A. R. Silva
2023-07-07 12:52 ` Linux regression tracking (Thorsten Leemhuis) [this message]
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=423a78fe-ac40-9983-ff44-90b1759fc0b5@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=gustavo@embeddedor.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=sudipm.mukherjee@gmail.com \
--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 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 NNTP newsgroup(s).