[Bug runtime/10301] New: adding '?' to the end of a probe results in a script failure when the probe point doesn't resolve

[Bug runtime/10301] New: adding '?' to the end of a probe results in a script failure when the probe point doesn't resolve

[jmoyer at redhat dot com]

# rpm -q systemtap
systemtap-0.9.8-1.fc9.x86_64

The probe in question is:

probe module("autofs4").statement("autofs4_expire_direct@fs/autofs4/expire.c+17") ?
{
	relative_path =	reverse_path_walk($mnt->mnt_mountpoint)
	root_path = reverse_path_walk($mnt->mnt_parent->mnt_mountpoint)
	printf("%s process %s[%d] expiring direct mount /%s/%s\n",
	       ctime(gettimeofday_s()), execname(), pid(),
	       root_path, relative_path)
}


[root@segfault tmp]# stap -g --vp 01 ./autofs.stp
semantic error: libdw failure (dwarf_entrypc): no error
Pass 2: analyzed script: 7 probe(s), 89 function(s), 2 embed(s), 8 global(s) in
70usr/130sys/204real ms.
Pass 2: analysis failed.  Try again with another '--vp 01' option.
[root@segfault tmp]# stap -g --vp 01 --vp 01 ./autofs.stp
probe autofs4_lookup@fs/autofs4/root.c:469 module=autofs4 reloc=.text
section=.text pc=0x97d462c
probe autofs4_follow_link@fs/autofs4/root.c:172 module=autofs4 reloc=.text
section=.text pc=0x97d3d39
probe autofs4_follow_link@fs/autofs4/symlink.c:16 module=autofs4 reloc=.text
section=.text pc=0x97d4d38
semantic error: libdw failure (dwarf_entrypc): no error
probe autofs4_expire_indirect@fs/autofs4/expire.c:290 module=autofs4 reloc=.text
section=.text pc=0x97d5813
probe autofs4_wait@fs/autofs4/waitq.c:321 module=autofs4 reloc=.text
section=.text pc=0x97d4ea4
probe autofs4_expire_indirect@fs/autofs4/expire.c:290 module=autofs4 reloc=.text
section=.text pc=0x97d5813
probe autofs4_wait@fs/autofs4/waitq.c:321 module=autofs4 reloc=.text
section=.text pc=0x97d4ea4
Pass 2: analyzed script: 7 probe(s), 89 function(s), 2 embed(s), 8 global(s) in
70usr/140sys/206real ms.
Pass 2: analysis failed.  Try again with another '--vp 01' option.
Running rm -rf /tmp/stapcdnNxO
[root@segfault tmp]# stap -g --vp 01 --vp 01 --vp 01 ./autofs.stp
blacklist regexps:
blfn:
^(atomic_notifier_call_chain|default_do_nmi|__die|die_nmi|do_debug|do_general_protection|do_int3|do_IRQ|do_page_fault|do_sparc64_fault|do_trap|dummy_nmi_callback|flush_icache_range|ia64_bad_break|ia64_do_page_fault|ia64_fault|io_check_error|mem_parity_error|nmi_watchdog_tick|notifier_call_chain|oops_begin|oops_end|program_check_exception|single_step_exception|sync_regs|unhandled_fault|unknown_nmi_error|.*raw_.*lock.*|.*read_.*lock.*|.*write_.*lock.*|.*spin_.*lock.*|.*rwlock_.*lock.*|.*rwsem_.*lock.*|.*mutex_.*lock.*|raw_.*|.*seq_.*lock.*|atomic_.*|atomic64_.*|get_bh|put_bh|.*apic.*|.*APIC.*|.*softirq.*|.*IRQ.*|.*_intr.*|__delay|.*kernel_text.*|get_current|current_.*|.*exception_tables.*|.*setup_rt_frame.*|.*preempt_count.*|preempt_schedule|__switch_to)$
blfn_ret: ^(do_exit|sys_exit|sys_exit_group)$
blfile:
^(kernel/kprobes.c|arch/.*/kernel/kprobes.c|include/asm/io.h|include/asm/bitops.h|arch/.*/include/asm/io.h|arch/.*/include/asm/bitops.h|drivers/ide/ide-iops.c)$
focused on module 'kernel = [0xffffffff81000000-0xffffffff81772d2c, bias 0x0]
file /usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/vmlinux ELF machine
|x86_64 (code 62)
focused on module 'kernel'
literal_stmt_for_pointer: finding value for dentry(arch/x86/kernel/init_task.c)
focused on module 'kernel = [0xffffffff81000000-0xffffffff81772d2c, bias 0x0]
file /usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/vmlinux ELF machine
|x86_64 (code 62)
focused on module 'kernel'
literal_stmt_for_pointer: finding value for dentry(arch/x86/kernel/init_task.c)
focused on module 'kernel = [0xffffffff81000000-0xffffffff81772d2c, bias 0x0]
file /usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/vmlinux ELF machine
|x86_64 (code 62)
focused on module 'kernel'
literal_stmt_for_pointer: finding value for dentry(arch/x86/kernel/init_task.c)
focused on module 'kernel = [0xffffffff81000000-0xffffffff81772d2c, bias 0x0]
file /usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/vmlinux ELF machine
|x86_64 (code 62)
focused on module 'kernel'
literal_stmt_for_pointer: finding value for dentry(arch/x86/kernel/init_task.c)
focused on module 'kernel = [0xffffffff81000000-0xffffffff81772d2c, bias 0x0]
file /usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/vmlinux ELF machine
|x86_64 (code 62)
focused on module 'kernel'
literal_stmt_for_pointer: finding value for path(arch/x86/kernel/head64.c)
focused on module 'kernel = [0xffffffff81000000-0xffffffff81772d2c, bias 0x0]
file /usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/vmlinux ELF machine
|x86_64 (code 62)
focused on module 'kernel'
literal_stmt_for_pointer: finding value for path(arch/x86/kernel/head64.c)
focused on module 'kernel = [0xffffffff81000000-0xffffffff81772d2c, bias 0x0]
file /usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/vmlinux ELF machine
|x86_64 (code 62)
focused on module 'kernel'
literal_stmt_for_pointer: finding value for vfsmount(init/do_mounts.c)
focused on module 'kernel = [0xffffffff81000000-0xffffffff81772d2c, bias 0x0]
file /usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/vmlinux ELF machine
|x86_64 (code 62)
focused on module 'kernel'
literal_stmt_for_pointer: finding value for vfsmount(init/do_mounts.c)
focused on module 'kernel = [0xffffffff81000000-0xffffffff81772d2c, bias 0x0]
file /usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/vmlinux ELF machine
|x86_64 (code 62)
focused on module 'kernel'
literal_stmt_for_pointer: finding value for vfsmount(init/do_mounts.c)
focused on module 'kernel = [0xffffffff81000000-0xffffffff81772d2c, bias 0x0]
file /usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/vmlinux ELF machine
|x86_64 (code 62)
focused on module 'kernel'
literal_stmt_for_pointer: finding value for vfsmount(init/do_mounts.c)
focused on module 'kernel = [0xffffffff81000000-0xffffffff81772d2c, bias 0x0]
file /usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/vmlinux ELF machine
|x86_64 (code 62)
focused on module 'kernel'
literal_stmt_for_pointer: finding value for dentry(arch/x86/kernel/init_task.c)
parsed 'autofs4_lookup' -> func 'autofs4_lookup'
focused on module 'autofs4 = [0x97d3200-0x97d9088, bias 0x0] file
/usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/kernel/fs/autofs4/autofs4.ko.debug
ELF machine |x86_64 (code 62)
focused on module 'autofs4'
selected function autofs4_lookup
probe autofs4_lookup@fs/autofs4/root.c:469 module=autofs4 reloc=.text
section=.text pc=0x97d462c
finding location for local 'nd' near address 0x97d462c, module bias 0x0
finding location for local 'dentry' near address 0x97d462c, module bias 0x0
parsed 'autofs4_follow_link' -> func 'autofs4_follow_link'
focused on module 'autofs4 = [0x97d3200-0x97d9088, bias 0x0] file
/usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/kernel/fs/autofs4/autofs4.ko.debug
ELF machine |x86_64 (code 62)
focused on module 'autofs4'
selected function autofs4_follow_link
probe autofs4_follow_link@fs/autofs4/root.c:172 module=autofs4 reloc=.text
section=.text pc=0x97d3d39
finding location for local 'nd' near address 0x97d3d39, module bias 0x0
selected function autofs4_follow_link
probe autofs4_follow_link@fs/autofs4/symlink.c:16 module=autofs4 reloc=.text
section=.text pc=0x97d4d38
finding location for local 'nd' near address 0x97d4d38, module bias 0x0
parsed 'autofs4_expire_direct@fs/autofs4/expire.c+17' -> func
'autofs4_expire_direct', file 'fs/autofs4/expire.c', line 0x7fff63efe944
focused on module 'autofs4 = [0x97d3200-0x97d9088, bias 0x0] file
/usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/kernel/fs/autofs4/autofs4.ko.debug
ELF machine |x86_64 (code 62)
focused on module 'autofs4'
selected source file 'fs/autofs4/expire.c'
examining inline instance of autofs4_expire_direct
selected inline instance of autofs4_expire_direct
entry-pc lookup (dwarf_ranges, ignored 1 more) = 0x97d5c79 (rc 0)
semantic error: libdw failure (dwarf_entrypc): no error
parsed 'autofs4_expire_indirect' -> func 'autofs4_expire_indirect'
focused on module 'autofs4 = [0x97d3200-0x97d9088, bias 0x0] file
/usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/kernel/fs/autofs4/autofs4.ko.debug
ELF machine |x86_64 (code 62)
focused on module 'autofs4'
selected function autofs4_expire_indirect
probe autofs4_expire_indirect@fs/autofs4/expire.c:290 module=autofs4 reloc=.text
section=.text pc=0x97d5813
literal_stmt_for_return: finding return value for
autofs4_expire_indirect(fs/autofs4/expire.c)
literal_stmt_for_return: finding return value for
autofs4_expire_indirect(fs/autofs4/expire.c)
parsed 'autofs4_wait' -> func 'autofs4_wait'
focused on module 'autofs4 = [0x97d3200-0x97d9088, bias 0x0] file
/usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/kernel/fs/autofs4/autofs4.ko.debug
ELF machine |x86_64 (code 62)
focused on module 'autofs4'
selected function autofs4_wait
probe autofs4_wait@fs/autofs4/waitq.c:321 module=autofs4 reloc=.text
section=.text pc=0x97d4ea4
literal_stmt_for_return: finding return value for autofs4_wait(fs/autofs4/waitq.c)
parsed 'autofs4_expire_indirect' -> func 'autofs4_expire_indirect'
focused on module 'autofs4 = [0x97d3200-0x97d9088, bias 0x0] file
/usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/kernel/fs/autofs4/autofs4.ko.debug
ELF machine |x86_64 (code 62)
focused on module 'autofs4'
selected function autofs4_expire_indirect
probe autofs4_expire_indirect@fs/autofs4/expire.c:290 module=autofs4 reloc=.text
section=.text pc=0x97d5813
finding location for local 'mnt' near address 0x97d5813, module bias 0x0
parsed 'autofs4_wait' -> func 'autofs4_wait'
focused on module 'autofs4 = [0x97d3200-0x97d9088, bias 0x0] file
/usr/lib/debug/lib/modules/2.6.27.15-78.2.23.fc9.x86_64/kernel/fs/autofs4/autofs4.ko.debug
ELF machine |x86_64 (code 62)
focused on module 'autofs4'
selected function autofs4_wait
probe autofs4_wait@fs/autofs4/waitq.c:321 module=autofs4 reloc=.text
section=.text pc=0x97d4ea4
finding location for local 'notify' near address 0x97d4ea4, module bias 0x0
finding location for local 'dentry' near address 0x97d4ea4, module bias 0x0
finding location for local 'dentry' near address 0x97d4ea4, module bias 0x0
Pass 2: analyzed script: 7 probe(s), 89 function(s), 2 embed(s), 8 global(s) in
60usr/150sys/219real ms.
Pass 2: analysis failed.  Try again with another '--vp 01' option.
Running rm -rf /tmp/stap1BqsYK

-- 
           Summary: adding '?' to the end of a probe results in a script
                    failure when the probe point doesn't resolve
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: jmoyer at redhat dot com


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

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

[Bug runtime/10301] adding '?' to the end of a probe results in a script failure when the probe point doesn't resolve

[jmoyer at redhat dot com]

------- Additional Comments From jmoyer at redhat dot com  2009-06-19 18:56 -------
Created an attachment (id=4010)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=4010&action=view)
probe mount/unmounts on automount-managed mount points


-- 


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

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

[Bug runtime/10301] adding '?' to the end of a probe results in a script failure when the probe point doesn't resolve

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2009-09-08 15:27 -------
Jeff, I believe the bulk of this problem has been fixed,
and I cannot reproduce it now.  Please recheck.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


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

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

[Bug runtime/10301] adding '?' to the end of a probe results in a script failure when the probe point doesn't resolve

[jmoyer at redhat dot com]

------- Additional Comments From jmoyer at redhat dot com  2009-09-08 19:56 -------
(In reply to comment #2)
> Jeff, I believe the bulk of this problem has been fixed,
> and I cannot reproduce it now.  Please recheck.

In what version?  The attached script doesn't even compile for me now under
kernel 2.6.30.5 using systemtap 0.9.9-3.

-- 


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

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

[Bug runtime/10301] adding '?' to the end of a probe results in a script failure when the probe point doesn't resolve

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2009-09-08 20:43 -------
> In what version?  The attached script doesn't even compile for me now under
> kernel 2.6.30.5 using systemtap 0.9.9-3.

The new kernel needs a new header for your embedded-c code.

%{
#include <linux/namei.h>
#include <linux/sched.h>
#include <linux/fs_struct.h>
%}

(#include in plain script is only a comment.)


-- 


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

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

[Bug runtime/10301] adding '?' to the end of a probe results in a script failure when the probe point doesn't resolve

[jmoyer at redhat dot com]

------- Additional Comments From jmoyer at redhat dot com  2009-09-08 20:50 -------
OK, I had added the include of fs_struct.h, but not the %{ %}.  That got it
compiled and loaded.  So, this seems to work, thanks!

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW


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

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

[Bug runtime/10301] adding '?' to the end of a probe results in a script failure when the probe point doesn't resolve

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2009-09-11 15:12 -------
working now

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


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

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