From: "gromero at linux dot vnet.ibm.com" <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: Mon, 24 Jun 2019 13:23:00 -0000 [thread overview]
Message-ID: <bug-24720-6586-KjkkLnTkQG@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 #7 from Gustavo Romero <gromero at linux dot vnet.ibm.com> ---
(In reply to Serhei Makarov from comment #6)
> Thanks for providing the detailed info. This problem was caused by the prior
> commit [1] attempting to fix a much rarer problem (a guru-mode module
> compiled for one kernel can sometimes run on a different kernel version if
> there is no difference in the ABIs checked by modsymversioning).
>
> [1]:
> https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;
> h=c8084763b75fe4c8c61a0ddfa69e2d13f04de18e;
> hp=3a29a2eef30f191afbc1bc117b6e5a2812dfe91b
>
> For now I reverted the commit in SystemTap git master since it clearly had
> undesirable results. I'll use your info to reproduce the problem for myself
> and see if there's a better way to fix it that works across all the
> different configs. Keeping the PR open to track that work.
Thanks for the analysis and explanations, Serhei!
If you need any help on reproducing/testing it please let me know.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-06-24 13: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 [this message]
2020-05-14 1:23 ` me at serhei dot io
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-KjkkLnTkQG@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).