From: Omar Sandoval <osandov@osandov.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Dimitri John Ledkov <dimitri.ledkov@surgut.co.uk>,
linux-kbuild@vger.kernel.org, Samir M <samir@linux.ibm.com>,
linux-kernel@vger.kernel.org,
Madhavan Srinivasan <maddy@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, stable@vger.kernel.org,
Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
linux-debuggers@vger.kernel.org, Nicolas Schier <nsc@kernel.org>,
Alexey Gladkov <legion@kernel.org>
Subject: Re: [mainline]Error while running make modules_install command
Date: Wed, 5 Nov 2025 13:53:13 -0800 [thread overview]
Message-ID: <aQvHSVXbOdiN_J5D@telecaster> (raw)
In-Reply-To: <20251105011548.GB769905@ax162>
On Tue, Nov 04, 2025 at 06:15:48PM -0700, Nathan Chancellor wrote:
> On Tue, Nov 04, 2025 at 08:35:57PM +0000, Dimitri John Ledkov wrote:
> > On Tue, 4 Nov 2025 at 18:12, Omar Sandoval <osandov@osandov.com> wrote:
> > > drgn's CI hit this same failure. FWIW, the commit fixed by this bisected
> > > commit, 3e86e4d74c04 ("kbuild: keep .modinfo section in
> > > vmlinux.unstripped"), also results in ELF segments of size 0 in vmlinux
> > > for some configurations, which confused drgn until I added a workaround
> > > (https://github.com/osandov/drgn/commit/2a9053de8796af866fd720a3c8c23013595d391a).
> > > So there's some funkiness in this area.
>
> Omar, could you provide me with a configuration file that reproduces
> this for you? Is there an easy way to check for this situation on the
> command line?
Here's a script that reproduces it:
```
#!/bin/sh
set -e
host_arch=x86_64
compiler_version="12.4.0"
compiler_dir="/tmp/arm64-gcc-$compiler_version"
if [ ! -e "$compiler_dir" ]; then
rm -rf "$compiler_dir.tmp"
mkdir "$compiler_dir.tmp"
curl -L "https://mirrors.kernel.org/pub/tools/crosstool/files/bin/$host_arch/$compiler_version/$host_arch-gcc-$compiler_version-nolibc-aarch64-linux.tar.xz" | tar -C "$compiler_dir.tmp" -Jx
mv "$compiler_dir.tmp" "$compiler_dir"
fi
export PATH="$compiler_dir/gcc-$compiler_version-nolibc/aarch64-linux/bin:$PATH"
make ARCH=arm64 CROSS_COMPILE=aarch64-linux- tinyconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux- -j$(nproc) vmlinux
readelf -W -l vmlinux | awk '$1 == "LOAD" && $6 ~ /0x0+\>/'
```
It prints something like:
LOAD 0x1ef008 0x0000000000000000 0xffff800080220000 0x000000 0x000000 R 0x10000
I.e., a segment with FileSiz and MemSiz 0.
Using a newer crosstool version fixes it, so maybe this was a GCC or
binutils bug.
Thanks,
Omar
next prev parent reply other threads:[~2025-11-05 21:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 11:17 [mainline]Error while running make modules_install command Samir M
2025-11-04 11:24 ` Venkat Rao Bagalkote
2025-11-04 18:12 ` Omar Sandoval
2025-11-04 20:35 ` Dimitri John Ledkov
2025-11-05 1:15 ` Nathan Chancellor
2025-11-05 12:51 ` Alexey Gladkov
2025-11-05 20:17 ` Nathan Chancellor
2025-11-05 21:53 ` Omar Sandoval [this message]
2025-11-06 1:08 ` Nathan Chancellor
2025-11-05 0:56 ` Nathan Chancellor
2025-11-05 9:22 ` Venkat Rao Bagalkote
2025-11-05 21:54 ` Omar Sandoval
2025-11-06 6:09 ` Samir M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aQvHSVXbOdiN_J5D@telecaster \
--to=osandov@osandov.com \
--cc=dimitri.ledkov@surgut.co.uk \
--cc=legion@kernel.org \
--cc=linux-debuggers@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=samir@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=venkat88@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.