From: "v.mayatskih at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/27465] ERROR: Couldn't insert module&Invalid module format
Date: Fri, 04 Feb 2022 19:22:02 +0000 [thread overview]
Message-ID: <bug-27465-6586-1o32eAwjs7@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 #5 from Vitaly Mayatskikh <v.mayatskih at gmail dot com> ---
check_version fails for module_layout:
204 insmod(43808): ->check_version info={.name="stap_30878",
.mod=0xffffa1dc617d1740, .hdr=0xffffa1dc617c1000, .len=142104,
.sechdrs=0xffffa1dc617e3098, .secstrings="", .strtab="", .symoffs=0,
.stroffs=0, .init_typeoffs=0, .core_typeoffs=0, .debug=0x0, .num_debug=0,
.sig_ok=0, .mod_kallsyms_init_off=0, .index={.sym=39, .str=40, .mod=34,
.vers=0, .info=21, .pcpu=32}} symname="module_layout" crc=-1290631832 mod=ERROR
207 insmod(43808): <-check_version return=0x0
This is for non-guru case (does not fail):
311 insmod(43893): ->check_version info={.name="stap_11738",
.mod=0xffffa1dc617d1c00, .hdr=0xffffa1dc617c1000, .len=139264,
.sechdrs=0xffffa1dc617e2540, .secstrings="", .strtab="", .symoffs=0,
.stroffs=0, .init_typeoffs=0, .core_typeoffs=0, .debug=0x0, .num_debug=0,
.sig_ok=0, .mod_kallsyms_init_off=0, .index={.sym=40, .str=41, .mod=35,
.vers=24, .info=21, .pcpu=33}} symname="module_layout" crc=-1290631832
mod=ERROR
319 insmod(43893): <-check_version return=0x1
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-02-04 19:22 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 [this message]
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
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-1o32eAwjs7@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).