All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: Jason Montleon <jmontleo@redhat.com>,
	linux-hardening@vger.kernel.org,
	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: Fri, 4 Oct 2024 10:56:21 -0700	[thread overview]
Message-ID: <202410041050.42575499F@keescook> (raw)
In-Reply-To: <0c9371f2-e8e9-479f-856d-408a81213747@ghiti.fr>

On Fri, Oct 04, 2024 at 01:37:44PM +0200, Alexandre Ghiti wrote:
> I have a question though: should we do something about the following
> warnings? Is there something wrong somewhere?
> 
> Wanted to write 8 to a 0-sized destination: oldptr at arch/riscv/errata/thead/errata.c:185
> Wanted to write 28 to a 0-sized destination: oldptr at arch/riscv/errata/thead/errata.c:185

I think it's a problem for fortify, not for the errata code. I'm
still looking into it -- they are unexpected warnings given the types
involved. I haven't been able to reproduce it in a stand-alone context
yet.

-- 
Kees Cook

WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <kees@kernel.org>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: Jason Montleon <jmontleo@redhat.com>,
	linux-hardening@vger.kernel.org,
	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: Fri, 4 Oct 2024 10:56:21 -0700	[thread overview]
Message-ID: <202410041050.42575499F@keescook> (raw)
In-Reply-To: <0c9371f2-e8e9-479f-856d-408a81213747@ghiti.fr>

On Fri, Oct 04, 2024 at 01:37:44PM +0200, Alexandre Ghiti wrote:
> I have a question though: should we do something about the following
> warnings? Is there something wrong somewhere?
> 
> Wanted to write 8 to a 0-sized destination: oldptr at arch/riscv/errata/thead/errata.c:185
> Wanted to write 28 to a 0-sized destination: oldptr at arch/riscv/errata/thead/errata.c:185

I think it's a problem for fortify, not for the errata code. I'm
still looking into it -- they are unexpected warnings given the types
involved. I haven't been able to reproduce it in a stand-alone context
yet.

-- 
Kees Cook

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

  reply	other threads:[~2024-10-04 17:56 UTC|newest]

Thread overview: 28+ 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-21 17:42 ` Jason Montleon
2024-09-22  2:42 ` Kees Cook
2024-09-22  2:42   ` Kees Cook
2024-09-22 20:18   ` Jason Montleon
2024-09-22 20:18     ` Jason Montleon
2024-09-22 22:37     ` Kees Cook
2024-09-22 22:37       ` Kees Cook
2024-09-24 15:58       ` Jason Montleon
2024-09-24 15:58         ` Jason Montleon
2024-09-24 17:36         ` Kees Cook
2024-09-24 17:36           ` Kees Cook
2024-09-25 14:32           ` Jason Montleon
2024-09-25 14:32             ` Jason Montleon
2024-10-01 14:28             ` Alexandre Ghiti
2024-10-01 14:28               ` Alexandre Ghiti
2024-10-02 15:14               ` Jason Montleon
2024-10-02 15:14                 ` Jason Montleon
2024-10-03 14:41                 ` Alexandre Ghiti
2024-10-03 14:41                   ` Alexandre Ghiti
2024-10-03 17:12                   ` Jason Montleon
2024-10-03 17:12                     ` Jason Montleon
2024-10-03 21:21                     ` Kees Cook
2024-10-03 21:21                       ` Kees Cook
2024-10-04 11:37                       ` Alexandre Ghiti
2024-10-04 11:37                         ` Alexandre Ghiti
2024-10-04 17:56                         ` Kees Cook [this message]
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=202410041050.42575499F@keescook \
    --to=kees@kernel.org \
    --cc=alex@ghiti.fr \
    --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 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.