This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug uprobes/7092] New: uprobes probes causing OOM


Using the test cases from bug 7082 modified to use uprobes instead of
uretprobes.  Here are the testcases:

[1]
# stap -ve 'probe process("bash").function("*") {}' -w -c bash
# exit

[2]
# stap -ve 'probe process("bash").function("*") {}' -w -c bash
# bash
# exit
# exit

[3]
# stap -ve 'probe process("bash").function("main") {}' -w -c bash
# exit

[4]
# stap -ve 'probe process("bash").function("main") {}' -w -c bash
# bash
# exit
# exit

On a 16-way i386 system running kernel 2.6.18-125.el5PAE (beta RHEL5.3), with
systemtap head, here are the test results:

[1] OOM.  When run, the machine gets an OOM in pass 5.  The bash prompt is never
seen.  On the console, I see:

agetty invoked oom-killer: gfp_mask=0xd0, order=0, oomkilladj=0
 [<c0457b31>] out_of_memory+0x72/0x1a5
 [<c0459006>] __alloc_pages+0x216/0x297
 [<c046db80>] cache_alloc_refill+0x26d/0x450
 [<c046d909>] kmem_cache_alloc+0x41/0x4b
 [<c047e134>] getname+0x1a/0xb0
 [<c046fe81>] do_sys_open+0x12/0xae
 [<c046ff4a>] sys_open+0x16/0x18
 [<c0404f17>] syscall_call+0x7/0xb

[2] same as [1]
[3] works
[4] works

-- 
           Summary: uprobes probes causing OOM
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: uprobes
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: dsmith at redhat dot com


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

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]