From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug uprobes/7092] New: uprobes probes causing OOM
Date: Wed, 10 Dec 2008 19:09:00 -0000 [thread overview]
Message-ID: <20081210190833.7092.dsmith@redhat.com> (raw)
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.
next reply other threads:[~2008-12-10 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 19:09 dsmith at redhat dot com [this message]
2008-12-10 19:53 ` Jim Keniston
2008-12-10 19:54 ` [Bug uprobes/7092] " jkenisto at us dot ibm dot com
2008-12-11 20:52 ` dsmith at redhat dot com
2008-12-15 19:26 ` dsmith at redhat dot com
2008-12-15 19:40 ` fche at redhat dot com
2009-03-06 17:28 ` fche at redhat dot com
2009-03-09 21:04 ` jkenisto at us dot ibm dot com
2009-03-09 21:06 ` 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=20081210190833.7092.dsmith@redhat.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).