linux-kernel - VirtualBox module build breakage since commit 39808e451fdf

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <392d86d2-76a4-03d2-5517-3c22bcf3e535@lwfinger.net>
Date:   Sun, 15 Dec 2019 20:48:01 -0600
From:   Larry Finger <Larry.Finger@...inger.net>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: VirtualBox module build breakage since commit 39808e451fdf

Hi,

Since commit 39808e451fdf ("kbuild: do not read 
$(KBUILD_EXTMOD)/Module.symvers"), some of the modules for VirtualBox have 
failed to build. There are at least 3 such modules, namely vboxdrv, vboxnetflt, 
and vboxnetadp. The latter 2 require linking to routines exported from the build 
of the first, thus file "Module.symvers" is copied from the build directory of 
vboxdrv into that of the other modules. Even though the documentation says that 
this method should work, and it has in the past, it fails after this commit. The 
necessary external symbols are not found.

Am I missing some step needed to make the copy of "Module.symvers" method work? 
I understand that the method could lead to stale values; however, the build of 
vboxdrv immediately precedes the build of the others, thus the values are always 
current.

Thanks,

Larry