linux-kernel - modpost Module.symver handling is broken in 5.6.0-rc7

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <931818529b1d4d13a08d30ddace22733@AcuMS.aculab.com>
Date:   Thu, 26 Mar 2020 16:25:23 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     Jessica Yu <jeyu@...nel.org>,
        'Linus Torvalds' <torvalds@...ux-foundation.org>
Subject: modpost Module.symver handling is broken in 5.6.0-rc7

Something is currently broken in modpost.
I'm guessing it is down to the recent patch that moved the
namespace back to the end of the line.

I'm building 2 'out of tree' modules that have a symbol dependency.
When I build the 2nd module I get ERROR "symbol" undefined message.

If I flip the order of the fields in Module.symver to the older order
and link with modpost from 5.4.0-rc7 (which I happen to have lurking)
it all works fine.

Note that I'm using a named namespace, not the default one
that is the full path of the module.

I'll dig in a little further.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)