public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/27465] ERROR: Couldn't insert module&Invalid module format
Date: Wed, 09 Feb 2022 23:57:47 +0000	[thread overview]
Message-ID: <bug-27465-6586-7sGPaIZff3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27465-6586@http.sourceware.org/bugzilla/>

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

--- Comment #8 from Frank Ch. Eigler <fche at redhat dot com> ---
modversion / module_layout checks tend to fail mainly if the system compiler
used to build the kernel is different enough from the one used to build
systemtap's kernel modules.  There are some gcc version-level features that
vary the struct-module and other data types in linux, so modversions machinery
can catch that.

I suggest checking compiler versions too.

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

  parent reply	other threads:[~2022-02-09 23:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25  2:13 [Bug runtime/27465] New: " lyeeer at outlook dot com
2021-03-02 20:14 ` [Bug runtime/27465] " fche at redhat dot com
2022-02-04 18:21 ` v.mayatskih at gmail dot com
2022-02-04 18:23 ` fche at redhat dot com
2022-02-04 18:53 ` v.mayatskih at gmail dot com
2022-02-04 19:22 ` v.mayatskih at gmail dot com
2022-02-04 19:30 ` v.mayatskih at gmail dot com
2022-02-04 19:40 ` v.mayatskih at gmail dot com
2022-02-09 23:57 ` fche at redhat dot com [this message]
2024-02-21 13:07 ` fche at redhat dot com

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-27465-6586-7sGPaIZff3@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).