From: Nathan Chancellor <nathan@kernel.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Objtool segfault inside an VM, based on commit 24172e0d7990
Date: Mon, 17 Nov 2025 10:50:41 -0700 [thread overview]
Message-ID: <20251117175041.GA703155@ax162> (raw)
In-Reply-To: <9cd36c00-b2e0-4d57-94b1-840b084d0a3b@gmx.com>
On Mon, Nov 17, 2025 at 03:40:35PM +1030, Qu Wenruo wrote:
>
>
> 在 2025/11/17 13:33, Qu Wenruo 写道:
> >
> >
> > 在 2025/11/17 13:10, Qu Wenruo 写道:
> > > Hi,
> > >
> > > Recently I'm hitting pretty frequent objtool crashes, sometimes
> > > during module linking (btrfs in my case) sometimes during the
> > > vmlinux linking.
> > >
> > > Unfortunately I don't have a coredump for it.
> > >
> > > The only info so far is from dmesg (and obvious the compile failure):
> > >
> > > [ 625.066787] traps: objtool[46220] general protection fault
> > > ip:563ab54c6eb0 sp:7ffd9c2ba7c8 error:0 in
> > > objtool[19eb0,563ab54b2000+1f000]
> > >
> > > The involved VM has the following spec:
> > >
> > > - Kernel branch
> > > Btrfs' development branch.
> > >
> > > The base commit is 24172e0d79900908cf5ebf366600616d29c9b417, around
> > > v6.18-rc6.
>
> Furthermore, if just compiling on old kernels (in my case, 6.17.8), I
> haven't yet hit a linking time segfault.
>
> So it's something in the v6.18 release cycle.
>
> Not sure if it's the recent Zen5 related hassles.
I had similar objtool crashes and David's fix [1] from another bug
report thread [2] appears to resolve this for me.
[1]: https://github.com/davidhildenbrand/linux/commit/58e62699f77738188730d489accd01ad8e3cdeeb
[2]: https://lore.kernel.org/20251117082023.90176-1-00107082@163.com/
Cheers,
Nathan
next prev parent reply other threads:[~2025-11-17 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 2:40 Objtool segfault inside an VM, based on commit 24172e0d7990 Qu Wenruo
2025-11-17 3:03 ` Qu Wenruo
2025-11-17 5:10 ` Qu Wenruo
2025-11-17 17:50 ` Nathan Chancellor [this message]
2025-11-17 20:27 ` Qu Wenruo
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=20251117175041.GA703155@ax162 \
--to=nathan@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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.