public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "srinivasa at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug testsuite/4337] New: testcases should know,whether debugfs is already mounted or not.
Date: Tue, 10 Apr 2007 06:23:00 -0000	[thread overview]
Message-ID: <20070410072302.4337.srinivasa@in.ibm.com> (raw)

My environment : kernel-2.6.21-rc6, elfutils-0.125 ,
systemtap(systemtap-20070407.tar.bz2)

When I executed systemtap testcases of this week
snapshot(systemtap-20070407.tar.bz2) with debugfs mounted, I saw below error.
=========================================================================
Running
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin1.exp
...
ERROR: tcl error sourcing
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin1.exp.
ERROR: 42
mount: debugfs already mounted or /sys/kernel/debug busy
mount: according to mtab, /debugfs is already mounted on /sys/kernel/debug
    while executing
"exec stap $test_file_name | hexdump $hex_args"
    (procedure "stap_run_binary" line 9)
    invoked from within
"stap_run_binary $srcdir/$subdir/$test.stp"
    (file
"/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin1.exp"
line 3)
    invoked from within
"source
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin1.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin1.exp"
    invoked from within
"catch "uplevel #0 source $test_file_name""
Running
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin2.exp
...
ERROR: tcl error sourcing
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin2.exp.
ERROR: 12 34 56 78 12 34 56 78
61 3d 12 20 62 3d 34 20
63 3d 56 20 64 3d 78
mount: debugfs already mounted or /sys/kernel/debug busy
mount: according to mtab, /debugfs is already mounted on /sys/kernel/debug
    while executing
"exec stap $test_file_name | hexdump $hex_args"
    (procedure "stap_run_binary" line 9)
    invoked from within
"stap_run_binary $srcdir/$subdir/$test.stp"
    (file
"/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin2.exp"
line 6)
    invoked from within
"source
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin2.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin2.exp"
    invoked from within
"catch "uplevel #0 source $test_file_name""
Running
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin3.exp
...
ERROR: tcl error sourcing
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin3.exp.
ERROR: 00 12 00 34 ab cd 56 78
56 78 ab cd 88 88 cd ef
61 3d 56 78 20 62 3d ab
cd 20 63 3d 88 88 20 64
3d cd ef
mount: debugfs already mounted or /sys/kernel/debug busy
mount: according to mtab, /debugfs is already mounted on /sys/kernel/debug
    while executing
"exec stap $test_file_name | hexdump $hex_args"
    (procedure "stap_run_binary" line 9)
    invoked from within
"stap_run_binary $srcdir/$subdir/$test.stp"
    (file
"/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin3.exp"
line 8)
    invoked from within
"source
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin3.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin3.exp"
    invoked from within
"catch "uplevel #0 source $test_file_name""
Running
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin4.exp
...
ERROR: tcl error sourcing
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin4.exp.
ERROR: 00 00 00 12 00 00 00 34
ab cd ef 00 00 00 56 78
12 34 56 78 11 11 22 22
88 88 99 99 cd ef 00 00
61 3d 12 34 56 78 20 62
3d 11 11 22 22 20 63 3d
88 88 99 99 20 64 3d cd
ef 00 00
mount: debugfs already mounted or /sys/kernel/debug busy
mount: according to mtab, /debugfs is already mounted on /sys/kernel/debug
    while executing
"exec stap $test_file_name | hexdump $hex_args"
    (procedure "stap_run_binary" line 9)
    invoked from within
"stap_run_binary $srcdir/$subdir/$test.stp"
    (file
"/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin4.exp"
line 11)
    invoked from within
"source
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin4.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin4.exp"
    invoked from within
"catch "uplevel #0 source $test_file_name""
Running
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin5.exp
...
ERROR: tcl error sourcing
/home/systemtap/tmp/stap_testing_200704090957/src/testsuite/systemtap.printf/bin5.exp.
ERROR: 00 00 00 00 00 00 00 12
00 00 00 00 00 00 00 34
ab cd 00 00 11 11 22 22
56 78 56 78 56 78 56 78
00 12 34 56 78 ab cd ef
11 11 22 22 33 33 44 44
88 88 99 99 aa aa bb bb
cd ef 00 00 11 11 22 22
61 3d 00 12 34 56 78 ab
cd ef 20 62 3d 11 11 22
22 33 33 44 44 20 63 3d
88 88 99 99 aa aa bb bb
20 64 3d cd ef 00 00 11
11 22 22
............................
=============================================
On reading the error, I unmounted the debugfs and run the tests, Now Iam not
facing any problems.
=====================================================
Running
/home/systemtap/tmp/stap_testing_200704100523/src/testsuite/systemtap.printf/bin1.exp
...
Running
/home/systemtap/tmp/stap_testing_200704100523/src/testsuite/systemtap.printf/bin2.exp
...
Running
/home/systemtap/tmp/stap_testing_200704100523/src/testsuite/systemtap.printf/bin3.exp
...
Running
/home/systemtap/tmp/stap_testing_200704100523/src/testsuite/systemtap.printf/bin4.exp
...
Running
/home/systemtap/tmp/stap_testing_200704100523/src/testsuite/systemtap.printf/bin5.exp
...
Running
/home/systemtap/tmp/stap_testing_200704100523/src/testsuite/systemtap.printf/int1.
===============================================================

So It would be good, if testcases are intelligent enough to make sure that
debugfs is already mounted or not.

-- 
           Summary: testcases should know,whether debugfs is already mounted
                    or not.
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: srinivasa at in dot ibm dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=4337

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

             reply	other threads:[~2007-04-10  6:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10  6:23 srinivasa at in dot ibm dot com [this message]
2007-04-10 13:12 ` [Bug testsuite/4337] " hunt 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=20070410072302.4337.srinivasa@in.ibm.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.com \
    /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).