public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Jason Montleon <jmontleo@redhat.com>, linux-hardening@vger.kernel.org
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
	linux-riscv@lists.infradead.org
Subject: Re: [REGRESSION][BISECTED] Cannot boot Lichee Pi 4A with FORTIFY_SOURCE enabled
Date: Sat, 21 Sep 2024 19:42:12 -0700	[thread overview]
Message-ID: <B2A62C7F-45BA-43E1-975F-5AF0197CD2C3@kernel.org> (raw)
In-Reply-To: <CAJD_bPJes4QhmXY5f63GHV9B9HFkSCoaZjk-qCT2NGS7Q9HODg@mail.gmail.com>



On September 21, 2024 10:42:11 AM PDT, Jason Montleon <jmontleo@redhat.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

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2024-09-22  2:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-21 17:42 [REGRESSION][BISECTED] Cannot boot Lichee Pi 4A with FORTIFY_SOURCE enabled Jason Montleon
2024-09-22  2:42 ` Kees Cook [this message]
2024-09-22 20:18   ` Jason Montleon
2024-09-22 22:37     ` Kees Cook
2024-09-24 15:58       ` Jason Montleon
2024-09-24 17:36         ` Kees Cook
2024-09-25 14:32           ` Jason Montleon
2024-10-01 14:28             ` Alexandre Ghiti
2024-10-02 15:14               ` Jason Montleon
2024-10-03 14:41                 ` Alexandre Ghiti
2024-10-03 17:12                   ` Jason Montleon
2024-10-03 21:21                     ` Kees Cook
2024-10-04 11:37                       ` Alexandre Ghiti
2024-10-04 17:56                         ` Kees Cook

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=B2A62C7F-45BA-43E1-975F-5AF0197CD2C3@kernel.org \
    --to=kees@kernel.org \
    --cc=jmontleo@redhat.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=regressions@lists.linux.dev \
    /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