From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 7F6783851C2E; Thu, 14 May 2020 01:23:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7F6783851C2E
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
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: systemtap
X-Bugzilla-Component: translator
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: me at serhei dot io
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: systemtap at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-24720-6586-th0v5BQm8l@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24720-6586@http.sourceware.org/bugzilla/>
References: <bug-24720-6586@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: systemtap@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Systemtap mailing list <systemtap.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/systemtap>,
 <mailto:systemtap-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/systemtap/>
List-Help: <mailto:systemtap-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/systemtap>,
 <mailto:systemtap-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2020 01:23:48 -0000

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

--- 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 is=
sue
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 form=
at

https://github.com/torvalds/linux/commit/43e24e82f35291d4c1ca78877ce1b20d3a=
eb78f1

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 str=
ict
vermagic check (the original cause of the issue) worked fine for me, so the=
re
is some additional condition present on the machine where it was reported.

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