linux-hardening - next-20250731: arm64 arc riscv64 parisc vmlinux.unstripped warning empty loadable segment detected at vaddr is this intentional?

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>] [day] [month] [year] [list]

Message-ID: <CA+G9fYvMS94GL5kMmHKSGSQqTS0XgwiYnETf_bLYYu6nTRNP-A@mail.gmail.com>
Date: Thu, 31 Jul 2025 19:41:50 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: open list <linux-kernel@...r.kernel.org>, linux-hardening@...r.kernel.org, 
	lkft-triage@...ts.linaro.org, Linux Regressions <regressions@...ts.linux.dev>
Cc: Masahiro Yamada <masahiroy@...nel.org>, kees@...nel.org, 
	"Gustavo A. R. Silva" <gustavoars@...nel.org>, Ben Copeland <benjamin.copeland@...aro.org>, 
	Arnd Bergmann <arnd@...db.de>, Anders Roxell <anders.roxell@...aro.org>, 
	Dan Carpenter <dan.carpenter@...aro.org>
Subject: next-20250731: arm64 arc riscv64 parisc vmlinux.unstripped warning
 empty loadable segment detected at vaddr is this intentional?

Regressions while building arm64 arc riscv64 parisc with defconfig
on the Linux next-20250730 and next-20250731 with gcc-13 and gcc-8
the following build warnings noticed.

Build warnings with gcc-13, gcc-12, gcc-11 and gcc-8 defconfig

Regression Analysis:
- New regression? Yes
- Reproducibility? Yes

First seen on the next-20250730
Good: next-20250729
Bad: next-20250730

Build regression: arm64  arc riscv64 parisc vmlinux.unstripped warning
empty loadable segment detected at vaddr is this intentional?

Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>

## Build log
aarch64-linux-gnu-objcopy: vmlinux.unstripped: warning: empty loadable
segment detected at vaddr=0xffff800082720000, is this intentional?
arc-elf32-objcopy: vmlinux.unstripped: warning: empty loadable segment
detected at vaddr=0x80306000, is this intentional?
riscv64-linux-gnu-objcopy: vmlinux.unstripped: warning: empty loadable
segment detected at vaddr=0xffffffff8202d000, is this intentional?
hppa-linux-gnu-objcopy: vmlinux.unstripped: warning: empty loadable
segment detected at vaddr=0x11400000, is this intentional?


## Source
* Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
* Git sha: 84b92a499e7eca54ba1df6f6c6e01766025943f1
* Git describe: next-20250731
* Project details:
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250731
* Architectures: arm64 arc riscv64 parisc
* Toolchains: gcc-8 gcc-13
* Kconfigs: defconfig

## Build
* Build details:
https://regressions.linaro.org/lkft/linux-next-master/next-20250731/log-parser-build-gcc/general-objcopy-warning-empty-loadable-segment-detected-at-vaddr-is-this-intentional/
* Build plan: https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/builds/30cmZFV63SOEwwWoGiSHEsDR63Q
* Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/30cmZFV63SOEwwWoGiSHEsDR63Q/
* Kernel config:
https://storage.tuxsuite.com/public/linaro/lkft/builds/30cmZFV63SOEwwWoGiSHEsDR63Q/config

## Steps to reproduce
 * tuxmake --runtime podman --target-arch arm64 --toolchain gcc-13
--kconfig defconfig

--
Linaro LKFT
https://lkft.linaro.org