From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Michal Kubecek <mkubecek@suse.cz>, Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: build failure after commit eb0481bbc4ce ("objtool: Fix reloc_hash size")
Date: Sat, 8 Jul 2023 15:40:50 +0200 [thread overview]
Message-ID: <fb93d107-c834-1849-2b14-1dd33c4f9955@leemhuis.info> (raw)
In-Reply-To: <20230628115825.ahqejf5y4hgxhyqj@lion.mk-sys.cz>
On 28.06.23 13:58, Michal Kubecek wrote:
>
> this morning, mainline kernel builds started to fail on my desktop like
> this:
>
> mike@lion:~/work/git/kernel-upstream> mkdir /srv/ram/kobj
> mike@lion:~/work/git/kernel-upstream> make -j24 CC=gcc-13 O=/srv/ram/kobj defconfig >/dev/null
> mike@lion:~/work/git/kernel-upstream> make -j24 CC=gcc-13 O=/srv/ram/kobj all >/dev/null
> net/ipv4/netfilter/iptable_nat.o: warning: objtool: mmap fail reloc
> net/netfilter/xt_mark.o: warning: objtool: mmap fail reloc
> net/netfilter/xt_nat.o: warning: objtool: mmap fail reloc
> net/netfilter/xt_LOG.o: warning: objtool: mmap fail reloc
> net/netfilter/xt_MASQUERADE.o: warning: objtool: mmap fail reloc
> net/netfilter/nf_log_syslog.o: warning: objtool: mmap fail reloc
> net/netfilter/xt_addrtype.o: warning: objtool: mmap fail reloc
> fs/efivarfs/efivarfs.o: warning: objtool: mmap fail reloc
> drivers/thermal/intel/x86_pkg_temp_thermal.o: warning: objtool: mmap fail reloc
> vmlinux.o: warning: objtool: mmap fail reloc
> incomplete ORC unwind tables in file: vmlinux
> Failed to sort kernel tables
> make[2]: *** [/home/mike/work/git/kernel-upstream/scripts/Makefile.vmlinux:35: vmlinux] Error 1
> make[2]: *** Deleting file 'vmlinux'
> make[1]: *** [/home/mike/work/git/kernel-upstream/Makefile:1256: vmlinux] Error 2
> make: *** [Makefile:226: __sub-make] Error 2
>
> I bisected the failure to commit
>
> eb0481bbc4ce ("objtool: Fix reloc_hash size")
>
> I also tried gcc11 and building on a normal filesystem (rather than
> tmpfs) but the result is still the same. Different configurations (e.g.
> allmodconfig) only show more modules with "mmap fail reloc". The machine
> has 64 GB of RAM and both ulimit -m and ulimit -v show "unlimited".
> Anything idea what else I should try?
Michal, thx for the report. Please correct me if I'm wrong: this as of
now is unfixed, as your patch to fix is afaics wasn't merged yet (at
least I can't see it even in next, but I might be missing something).
Hence adding it to the regression tracking now that the end of the merge
window is near:
#regzbot ^introduced eb0481bbc4ce
#regzbot title objtool: build failure
#regzbot monitor:
https://lore.kernel.org/all/20230629102051.42E8360467@lion.mk-sys.cz/
#regzbot fix: objtool: initialize all of struct elf
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
next prev parent reply other threads:[~2023-07-08 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 11:58 build failure after commit eb0481bbc4ce ("objtool: Fix reloc_hash size") Michal Kubecek
2023-06-28 15:16 ` Josh Poimboeuf
2023-06-28 15:44 ` Michal Kubecek
2023-06-28 16:06 ` Michal Kubecek
2023-06-28 16:45 ` Michal Kubecek
2023-06-28 17:05 ` Josh Poimboeuf
2023-06-28 17:26 ` Michal Kubecek
2023-06-28 18:10 ` Josh Poimboeuf
2023-06-28 19:32 ` Peter Zijlstra
2023-07-08 13:40 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-07-09 14:09 ` Michal Kubecek
2023-07-10 17:16 ` Josh Poimboeuf
2023-07-16 22:56 ` Michal Kubecek
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=fb93d107-c834-1849-2b14-1dd33c4f9955@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).