Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   David Laight <David.Laight@ACULAB.COM>
To:     "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
CC:     Jessica Yu <jeyu@kernel.org>,
        'Linus Torvalds' <torvalds@linux-foundation.org>
Subject: modpost Module.symver handling is broken in 5.6.0-rc7
Thread-Topic: modpost Module.symver handling is broken in 5.6.0-rc7
Thread-Index: AdYDiqOPE71nee/CTfS3aDSZbkO5Jw==
Date:   Thu, 26 Mar 2020 16:25:23 +0000
Message-ID: <931818529b1d4d13a08d30ddace22733@AcuMS.aculab.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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)