public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "lyeeer at outlook dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/27465] New: ERROR: Couldn't insert module&Invalid module format
Date: Thu, 25 Feb 2021 02:13:42 +0000	[thread overview]
Message-ID: <bug-27465-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27465
           Summary: ERROR: Couldn't insert module&Invalid module format
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: lyeeer at outlook dot com
  Target Milestone: ---

Created attachment 13262
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13262&action=edit
Execute script, used to get system calls of docker during execution

Hello, When I use the systemTap4.4 version to test on an Ubuntu system with a
kernel version of 4.4.0-21, the following problems occur.

ly@ubuntu:~/Desktop/LiCShield-master/LiCShield-master$ sudo stap -g
/home/ly/Desktop/LiCShield-master/LiCShield-master/tracing_tool/systemtap_scripts/tracer.stp
-DSTP_NO_OVERLOAD -DMAXSTRINGLEN=4096 -v -c /usr/bin/docker -d -o
/home/ly/Desktop/LiCShield-master/LiCShield-master/training_session/python_build 

Pass 1: parsed user script and 480 library scripts using
124352virt/93704res/5424shr/88676data kb, in 340usr/100sys/434real ms. WARNING:
confusing usage, consider @entry($file) in .return probe: identifier '$file' at
/home/ly/Desktop/LiCShield-master/LiCShield-master/tracing_tool/systemtap_scripts/tracer.stp:380:43
source: path_arg[tid()] = get_path_wrapper(NULL, $file, %{ FILE %}) ^ WARNING:
confusing usage, consider @entry($new_dir->mnt) in .return probe: identifier
'$new_dir' at :391:30 source: old_path = get_path_wrapper($new_dir->mnt,
$old_dentry, %{ DENTRY %}) ^ WARNING: confusing usage, consider
@entry($old_dentry) in .return probe: identifier '$old_dentry' at :391:45
source: old_path = get_path_wrapper($new_dir->mnt, $old_dentry, %{ DENTRY %}) ^
WARNING: confusing usage, consider @entry($new_dir->mnt) in .return probe:
identifier '$new_dir' at :392:29 source: path = get_path_wrapper($new_dir->mnt,
$new_dentry, %{ DENTRY %}) ^ WARNING: confusing usage, consider
@entry($new_dentry) in .return probe: identifier '$new_dentry' at :392:44
source: path = get_path_wrapper($new_dir->mnt, $new_dentry, %{ DENTRY %}) ^
WARNING: confusing usage, consider @entry($old_dir->mnt) in .return probe:
identifier '$old_dir' at :406:30 source: old_path =
get_path_wrapper($old_dir->mnt, $old_dentry, %{ DENTRY %}) ^ WARNING: confusing
usage, consider @entry($old_dentry) in .return probe: identifier '$old_dentry'
at :406:45 source: old_path = get_path_wrapper($old_dir->mnt, $old_dentry, %{
DENTRY %}) ^ WARNING: confusing usage, consider @entry($new_dir->mnt) in
.return probe: identifier '$new_dir' at :407:29 source: path =
get_path_wrapper($new_dir->mnt, $new_dentry, %{ DENTRY %}) ^ WARNING: confusing
usage, consider @entry($new_dentry) in .return probe: identifier '$new_dentry'
at :407:44 source: path = get_path_wrapper($new_dir->mnt, $new_dentry, %{
DENTRY %}) ^ WARNING: confusing usage, consider @entry($old_dentry) in .return
probe: identifier '$old_dentry' at :411:19 source:
if(is_dentry_dir($old_dentry)) ^ WARNING: confusing usage, consider
@entry($path) in .return probe: identifier '$path' at :563:50 source:
mount_target[tid] = get_path_wrapper(NULL, $path, %{ PATH %}) ^ WARNING:
confusing usage, consider @entry($path) in .return probe: identifier '$path' at
:567:47 source: mount_source[tid] = get_path_wrapper(NULL, $path, %{ PATH %}) ^
Pass 2: analyzed script: 34 probes, 33 functions, 100 embeds, 8 globals using
176924virt/147968res/6892shr/141248data kb, in 1170usr/860sys/2376real ms.
WARNING: unused command line option $1/@1 
Pass 3: using cached
/home/ly/.systemtap/cache/80/stap_80a92b209efe4091f63377f31abb085e_93148.c 
Pass 4: using cached
/home/ly/.systemtap/cache/80/stap_80a92b209efe4091f63377f31abb085e_93148.ko 
Pass 5: starting run. ERROR: Couldn't insert module
'/tmp/stapaon1yo/stap_80a92b209efe4091f63377f31abb085e_93148.ko': Invalid
module format WARNING: /usr/local/bin/staprun exited with status: 1 
Pass 5: run completed in 0usr/0sys/2real ms. Pass 5: run failed. [man
error::pass5]

Then, I searched for a related answer(Bug 24720) that said it was a problem
with guru mode. But the C language code is embedded in my script, so I need to
turn on the guru mode. If it is not turned on, an error will occur

ly@ubuntu:~/Desktop/LiCShield-master/LiCShield-master$ sudo stap
/home/ly/Desktop/LiCShield-master/LiCShield-master/tracing_tool/systemtap_scripts/tracer.stp
-v -c /usr/bin/docker -d -o
/home/ly/Desktop/LiCShield-master/LiCShield-master/training_session/python_build
parse error: embedded code in unprivileged script; need stap -g saw:
embedded-code at
/home/ly/Desktop/LiCShield-master/LiCShield-master/tracing_tool/systemtap_scripts/tracer.stp:1:1
source: ...

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

             reply	other threads:[~2021-02-25  2:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25  2:13 lyeeer at outlook dot com [this message]
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
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@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).