[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y8hQbC3wvu1S+uZ5@zn.tnic>
Date: Wed, 18 Jan 2023 21:02:52 +0100
From: Borislav Petkov <bp@...en8.de>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: Petr Mladek <pmladek@...e.com>,
Prarit Bhargava <prarit@...hat.com>,
Vegard Nossum <vegard.nossum@...cle.com>,
NeilBrown <neilb@...e.de>, Goldwyn Rodrigues <rgoldwyn@...e.com>,
Petr Pavlu <petr.pavlu@...e.com>, david@...hat.com,
mwilck@...e.com, linux-modules@...r.kernel.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH v2] module: Don't wait for GOING modules
On Tue, Jan 17, 2023 at 04:04:22PM -0800, Luis Chamberlain wrote:
> and now I'm seeing this while trying to build v5.1:
>
> ld: arch/x86/boot/compressed/pgtable_64.o:(.bss+0x0): multiple definition of `__force_order';
> arch/x86/boot/compressed/kaslr_64.o:(.bss+0x0): first defined here
You need to backport
aa5cacdc29d7 ("x86/asm: Replace __force_order with a memory clobber")
for that.
Happens when building older kernels with newer toolchain.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists