public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/24720] stap Can't insert module and exit with error "Invalid module format"
Date: Thu, 14 May 2020 01:23:48 +0000	[thread overview]
Message-ID: <bug-24720-6586-th0v5BQm8l@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24720-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24720

--- Comment #8 from Serhei Makarov <me at serhei dot io> ---
Checked back on this since I want to re-enable the strict vermagic checking for
the upcoming stap release. Unfortunately, what prevented diagnosing this issue
back when this PR was filed is that stap -v does not share the full error
message when loading the module, only the last line (based on the modprobe
error code, see moderror() in staprun/staprun_func.c).

One example of a situation where vermagic might be mismatched (on ppc,
interestingly enough, just as with the original problem report) has a full
message along the following lines:

  # insmod autofs4-pg.ko
  autofs4: version magic
  '4.11.0-rc3-gcc-5.4.1-00017-g5a61ef74f269 SMP mod_unload modversions '
  should be
  '4.11.0-rc3-gcc-5.4.1-00017-g5a61ef74f269-dirty SMP mod_unload modversions
mprofile-kernel'
  insmod: ERROR: could not insert module autofs4-pg.ko: Invalid module format

https://github.com/torvalds/linux/commit/43e24e82f35291d4c1ca78877ce1b20d3aeb78f1

Not sure if it's related to the original reported situation.

* * *

I went back to a powerpc machine to repro the problem, but enabling the strict
vermagic check (the original cause of the issue) worked fine for me, so there
is some additional condition present on the machine where it was reported.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2020-05-14  1:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 19:34 [Bug translator/24720] New: " gromero at linux dot vnet.ibm.com
2019-06-21 19:35 ` [Bug translator/24720] " gromero at linux dot vnet.ibm.com
2019-06-21 19:47 ` gromero at linux dot vnet.ibm.com
2019-06-21 19:49 ` gromero at linux dot vnet.ibm.com
2019-06-21 19:50 ` gromero at linux dot vnet.ibm.com
2019-06-21 19:50 ` gromero at linux dot vnet.ibm.com
2019-06-21 20:00 ` gromero at linux dot vnet.ibm.com
2019-06-21 22:10 ` me at serhei dot io
2019-06-24 13:23 ` gromero at linux dot vnet.ibm.com
2020-05-14  1:23 ` me at serhei dot io [this message]

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=bug-24720-6586-th0v5BQm8l@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).