lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <B2A62C7F-45BA-43E1-975F-5AF0197CD2C3@kernel.org> Date: Sat, 21 Sep 2024 19:42:12 -0700 From: Kees Cook <kees@...nel.org> To: Jason Montleon <jmontleo@...hat.com>, linux-hardening@...r.kernel.org CC: Linux regressions mailing list <regressions@...ts.linux.dev>, linux-riscv@...ts.infradead.org Subject: Re: [REGRESSION][BISECTED] Cannot boot Lichee Pi 4A with FORTIFY_SOURCE enabled On September 21, 2024 10:42:11 AM PDT, Jason Montleon <jmontleo@...hat.com> wrote: >Starting with 6.11-rc1 I can no longer boot the Lichee Pi 4A with >FORTIFY_SOURCE enabled. This works on 6.10 up to at least 6.10.11. >However, with 6.11 I get no output at all from the kernel on the >serial console with FORTIFY_SOURCE enabled and the system never comes >online on network or otherwise as far as I can tell. > >I did a bisect which led to: >2003e483a81cc235e29f77da3f6b256cb4b348e7 >fortify: Do not special-case 0-sized destinations > >If I revert this commit I can once again boot the Lichee Pi 4A with >FORTIFY_SOURCE enabled. > Thanks for the report! Are you able to catch what the error log shows? There must be some 0-sized array that snuck by. Can you share your .config and compiler version? -Kees -- Kees Cook
Powered by blists - more mailing lists