[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250311181056.GF3493@redhat.com>
Date: Tue, 11 Mar 2025 19:10:57 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Ard Biesheuvel <ardb@...nel.org>, Brian Gerst <brgerst@...il.com>,
linux-kernel@...r.kernel.org, x86@...nel.org,
Ingo Molnar <mingo@...nel.org>, "H . Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Uros Bizjak <ubizjak@...il.com>, stable@...r.kernel.org,
Fangrui Song <i@...kray.me>, Nathan Chancellor <nathan@...nel.org>,
Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH] x86/stackprotector: fix build failure with
CONFIG_STACKPROTECTOR=n
On 03/11, Borislav Petkov wrote:
>
> On Tue, Mar 11, 2025 at 03:37:25PM +0100, Oleg Nesterov wrote:
> > sorry for the off-topic noise, but what about the
> >
> > [PATCH] x86/stackprotector: fix build failure with CONFIG_STACKPROTECTOR=n
> > https://lore.kernel.org/all/20241206123207.GA2091@redhat.com/
> >
> > fix for the older binutils? It was acked by Ard.
> >
> > Should I resend it?
>
> Can you pls explain how you trigger this?
>
> I just did a
>
> # CONFIG_STACKPROTECTOR is not set
>
> build here and it was fine.
>
> So there's something else I'm missing.
See the "older binutils?" above ;)
my toolchain is quite old,
$ ld -v
GNU ld version 2.25-17.fc23
but according to Documentation/process/changes.rst
binutils 2.25 ld -v
it should be still supported.
Oleg.
Powered by blists - more mailing lists