On Thu, Oct 3, 2024 at 10:41 AM Alexandre Ghiti wrote:
>
> Hi Jason,
>
> On 02/10/2024 17:14, Jason Montleon wrote:
> > On Tue, Oct 1, 2024 at 10:53 AM Alexandre Ghiti wrote:
> >> Hi Jason,
> >>
> >> On 25/09/2024 16:32, Jason Montleon wrote:
&g
On Tue, Oct 1, 2024 at 10:53 AM Alexandre Ghiti wrote:
>
> Hi Jason,
>
> On 25/09/2024 16:32, Jason Montleon wrote:
> > On Tue, Sep 24, 2024 at 1:36 PM Kees Cook wrote:
> >>
> >>
> >> On September 24, 2024 8:58:57 AM PDT, Jason Montleon
> >
On Tue, Sep 24, 2024 at 1:36 PM Kees Cook wrote:
>
>
>
> On September 24, 2024 8:58:57 AM PDT, Jason Montleon
> wrote:
> >On Sun, Sep 22, 2024 at 6:38 PM Kees Cook wrote:
> >> Can you try this patch? It should avoid using the "WARN" infrastructure
>
.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/riscv/kernel/alternative.c?h=v6.11#n214
I didn't want to give up so I wrote a simple module to figure out how
to use sbi_ecall and then incorporated that idea into your patch,
although even that was not straightforward:
https://gist.github.com/jmontleon/f3536ad70dc92bed992139ad5b266d5c
Full output: https://gist.github.com/jmontleon/823facff38e28b717f153e38adcfd7fe
Thank you again,
Jason Montleon
--
Jason Montleon| email: jmont...@redhat.com
Red Hat, Inc. | gpg key: 0x069E3022
Cell: 508-496-0663| irc: jmontleo / jmontleon
On Sat, Sep 21, 2024 at 10:42 PM Kees Cook wrote:
>
>
>
> On September 21, 2024 10:42:11 AM PDT, Jason Montleon
> 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.
>
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.
Thank you,
Jason Montleon
