public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: Jan Stancek <jstancek@redhat.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	arnd@arndb.de
Subject: Re: unable to load modules with CONFIG_MODVERSIONS=y after commit 8ab2ae655b
Date: Tue, 6 Dec 2016 14:44:54 +0100	[thread overview]
Message-ID: <20161206134454.GA13814@angband.pl> (raw)
In-Reply-To: <656276734.2322009.1481031061742.JavaMail.zimbra@redhat.com>

On Tue, Dec 06, 2016 at 08:31:01AM -0500, Jan Stancek wrote:
> Starting with 4.9-rc8 / commit 8ab2ae655b ("default exported asm symbols to zero")
> I'm running into issue with kernel built with CONFIG_MODVERSIONS=y
> and (older) binutils (binutils-2.25.1-20.base.el7.ppc64le). 
> 
> Modules fail to load, for example:
> 
> [    3.163646] Found checksum 0 vs module 4829A47E 
> [    3.163787] dm_mod: disagrees about version of symbol memcpy 
> [    3.163862] dm_mod: Unknown symbol memcpy (err -22)
> 
> Bisect led me to 8ab2ae655b, reverting it allows boot to
> progress as before.

powerpc happens to be the only arch that actually followed the plan and
implemented asm-prototypes.h (not including Debian which applied my patch to
do so on x86, that patch is not in mainline).

Could you try reverting commits that add exports to that file?

-- 
u-boot problems can be solved with the help of your old SCSI manuals, the
parts that deal with goat termination.  You need a black-handled knife, and
an appropriate set of candles (number and color matters).  Or was it a
silver-handled knife?  Crap, need to look that up.

  reply	other threads:[~2016-12-06 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2124400518.2319293.1481030523351.JavaMail.zimbra@redhat.com>
2016-12-06 13:31 ` unable to load modules with CONFIG_MODVERSIONS=y after commit 8ab2ae655b Jan Stancek
2016-12-06 13:44   ` Adam Borowski [this message]
2016-12-06 16:39     ` Linus Torvalds
2016-12-07 23:12       ` Arnd Bergmann
2016-12-06 23:28 Philip Müller

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=20161206134454.GA13814@angband.pl \
    --to=kilobyte@angband.pl \
    --cc=arnd@arndb.de \
    --cc=jstancek@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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