From: Nathan Chancellor <nathan@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Rainer Fiebig <jrf@mailbox.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
jpoimboe@kernel.org
Subject: Re: 6.18.14: VirtualBox modules don't build anymore; bisected
Date: Fri, 27 Feb 2026 22:48:50 -0700 [thread overview]
Message-ID: <20260228054850.GA2321895@ax162> (raw)
In-Reply-To: <2026022738-tricky-popper-c70e@gregkh>
On Fri, Feb 27, 2026 at 08:29:05PM -0500, Greg KH wrote:
> On Sat, Feb 28, 2026 at 12:30:29AM +0100, Rainer Fiebig wrote:
> > Am 27.02.26 um 21:12 schrieb Greg KH:
> > > On Fri, Feb 27, 2026 at 04:33:34PM +0100, Rainer Fiebig wrote:
> > >> In case this hasn't been reported already: with 6.18.14 the
> > >> VirtualBox-7.1.16 modules won't build during the boot process, as they
> > >> usually do. Bisecting between 6.18.13/14 led to this:
> > >>
> > >> f056c340b73962ebaffe93997b582bdf16dc6270 is the first bad commit
> > >> commit f056c340b73962ebaffe93997b582bdf16dc6270 (HEAD)
> > >> Author: Josh Poimboeuf <jpoimboe@kernel.org>
> > >> Date: Tue Feb 10 13:45:22 2026 -0800
> > >>
> > >> kbuild: Add objtool to top-level clean target
> > >>
> > >> [ Upstream commit 68b4fe32d73789dea23e356f468de67c8367ef8f ]
> > >>
> > >> Objtool is an integral part of the build, make sure it gets cleaned
> > >> by "make clean" and "make mrproper".
> > >> [...]
> > >>
> > >>
> > >> The script I use for building my kernels includes "make mrproper" before
> > >> compiling and "make clean" after the kernel and modules have been
> > >> installed.
> > >>
> > >> Perhaps it would be more appropriate to report this to the
> > >> VirtualBox-devs but I won't do that because the registration procedure
> > >> asks for too many private data.
> > >
> > > We obviously can not do anything about external modules, so if you rely
> > > on these, you are going to have to work with them on this, sorry.
> >
> > Alright, tough luck. But that a patch-release of an LTS-kernel breaks
> > VirtualBox is really a first - at least as far as I can remember.
>
> Then they have gotten really lucky :)
I think this is firmly a Kbuild bug, as we broke the contract of
'make clean' leaving around enough to build external modules:
https://lore.kernel.org/20260227-avoid-objtool-binary-removal-clean-v1-1-122f3e55eae9@kernel.org/
Kbuild is what runs objtool, not the external module itself. I don't
care much for external modules but this does not appear to be something
they have done or relied on.
Cheers,
Nathan
next prev parent reply other threads:[~2026-02-28 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 15:33 6.18.14: VirtualBox modules don't build anymore; bisected Rainer Fiebig
2026-02-27 20:12 ` Greg KH
2026-02-27 23:30 ` Rainer Fiebig
2026-02-28 1:29 ` Greg KH
2026-02-28 5:48 ` Nathan Chancellor [this message]
2026-02-28 10:37 ` Rainer Fiebig
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=20260228054850.GA2321895@ax162 \
--to=nathan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@kernel.org \
--cc=jrf@mailbox.org \
--cc=stable@vger.kernel.org \
/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