linux-kernel - Re: linux-next: build failure after merge of the mm-nonmm-unstable tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <fcc9ca3e-8c04-43c0-606c-e798bc0cf9ce@linux-m68k.org>
Date: Sun, 21 Dec 2025 13:58:17 +1100 (AEDT)
From: Finn Thain <fthain@...ux-m68k.org>
To: Peter Zijlstra <peterz@...radead.org>, Ard Biesheuvel <ardb@...nel.org>
cc: Andrew Morton <akpm@...ux-foundation.org>, Will Deacon <will@...nel.org>, 
    Arnd Bergmann <arnd@...db.de>, Stephen Rothwell <sfr@...b.auug.org.au>, 
    x86@...nel.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
    Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the mm-nonmm-unstable
 tree


On Thu, 18 Dec 2025, Stephen Rothwell wrote:

> After merging the mm-nonmm-unstable tree, today's linux-next build
> (x86_64 allmodconfig) failed like this:
> 
> x86_64-linux-gnu-ld: error: unplaced orphan section `__bug_table' from `arch/x86/boot/compressed/sev-handle-vc.o'
> 

I found that I could reproduce the same build failure after applying 
Peter's patch to v6.19-rc1. So it's not confined to linux-next. I used 
allnoconfig with CONFIG_LD_ORPHAN_WARN_LEVEL=error and 
CONFIG_AMD_MEM_ENCRYPT=y because allmodconfig takes forever to build.

The patch in question is this one:
https://lore.kernel.org/lkml/0c18fd08ef19497768070783da28086e01d11a00.1765866665.git.fthain@linux-m68k.org/

I may have found a solution for the problem, but I don't understand this 
code, so I've Cc'd Ard et al. I don't know whether the __bug_table section 
is relevant to sev-handle-vc.c. If that section is not desired, I propose 
to make this change to Peter's patch --

diff --git a/include/linux/instrumented.h b/include/linux/instrumented.h
index 402a999a0d6b..d39d89206561 100644
--- a/include/linux/instrumented.h
+++ b/include/linux/instrumented.h
@@ -68,7 +68,9 @@ static __always_inline void instrument_atomic_read(const volatile void *v, size_
 {
 	kasan_check_read(v, size);
 	kcsan_check_atomic_read(v, size);
+#ifndef __DISABLE_EXPORTS
 	WARN_ON_ONCE(IS_ENABLED(CONFIG_DEBUG_ATOMIC) && ((unsigned long)v & (size - 1)));
+#endif
 }
 
 /**
@@ -83,7 +85,9 @@ static __always_inline void instrument_atomic_write(const volatile void *v, size
 {
 	kasan_check_write(v, size);
 	kcsan_check_atomic_write(v, size);
+#ifndef __DISABLE_EXPORTS
 	WARN_ON_ONCE(IS_ENABLED(CONFIG_DEBUG_ATOMIC) && ((unsigned long)v & (size - 1)));
+#endif
 }
 
 /**
@@ -98,7 +102,9 @@ static __always_inline void instrument_atomic_read_write(const volatile void *v,
 {
 	kasan_check_write(v, size);
 	kcsan_check_atomic_read_write(v, size);
+#ifndef __DISABLE_EXPORTS
 	WARN_ON_ONCE(IS_ENABLED(CONFIG_DEBUG_ATOMIC) && ((unsigned long)v & (size - 1)));
+#endif
 }
 
 /**


The next patch in the series needs a similar change, which I've also 
pushed to my github repo at
https://github.com/fthain/linux/commits/atomic_t