public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* [Bug runtime/7016] New: Systemtap will causes OOM when specifying large relay buffer size.
@ 2008-11-10 17:11 mhiramat at redhat dot com
  2008-11-10 17:14 ` [Bug runtime/7016] " mhiramat at redhat dot com
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: mhiramat at redhat dot com @ 2008-11-10 17:11 UTC (permalink / raw)
  To: systemtap

When I specified larger value than main memory, to -s option of systemtap, the
system ran OOM killer and stopped on ia64 and x86-64. I couldn't reproduce it on
ia32 because it's vmalloc-space is smaller than real memory.

For example, if the machine has 4GB memory, run
# stap -e 'probe begin{hello}' -s 4095
this causes OOM kill.

if the machine has 8GB memory and 4 CPUs, run
# stap -e 'probe begin{hello}' -s 2048 -b

This is always reproducible on 64-bit arch.

I think stap should fail to run if the system doesn't have enough free memory.

-- 
           Summary: Systemtap will causes OOM when specifying large relay
                    buffer size.
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: mhiramat at redhat dot com


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

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug runtime/7016] Systemtap will causes OOM when specifying large relay buffer size.
  2008-11-10 17:11 [Bug runtime/7016] New: Systemtap will causes OOM when specifying large relay buffer size mhiramat at redhat dot com
@ 2008-11-10 17:14 ` mhiramat at redhat dot com
  2008-11-10 18:42 ` fche at redhat dot com
  2008-11-10 19:25 ` mhiramat at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: mhiramat at redhat dot com @ 2008-11-10 17:14 UTC (permalink / raw)
  To: systemtap


------- Additional Comments From mhiramat at redhat dot com  2008-11-10 17:13 -------
Users in stapusr group can cause OOM killer, because the size of relayfs is just
a runtime option of staprun.


-- 


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

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug runtime/7016] Systemtap will causes OOM when specifying large relay buffer size.
  2008-11-10 17:11 [Bug runtime/7016] New: Systemtap will causes OOM when specifying large relay buffer size mhiramat at redhat dot com
  2008-11-10 17:14 ` [Bug runtime/7016] " mhiramat at redhat dot com
@ 2008-11-10 18:42 ` fche at redhat dot com
  2008-11-10 19:25 ` mhiramat at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: fche at redhat dot com @ 2008-11-10 18:42 UTC (permalink / raw)
  To: systemtap


------- Additional Comments From fche at redhat dot com  2008-11-10 18:41 -------
Perhaps relay_open* could be taught to use GFP_ATOMIC | GFP_NORETRY.

-- 


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

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug runtime/7016] Systemtap will causes OOM when specifying large relay buffer size.
  2008-11-10 17:11 [Bug runtime/7016] New: Systemtap will causes OOM when specifying large relay buffer size mhiramat at redhat dot com
  2008-11-10 17:14 ` [Bug runtime/7016] " mhiramat at redhat dot com
  2008-11-10 18:42 ` fche at redhat dot com
@ 2008-11-10 19:25 ` mhiramat at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: mhiramat at redhat dot com @ 2008-11-10 19:25 UTC (permalink / raw)
  To: systemtap


------- Additional Comments From mhiramat at redhat dot com  2008-11-10 19:24 -------
(In reply to comment #2)
> Perhaps relay_open* could be taught to use GFP_ATOMIC | GFP_NORETRY.

Indeed. However, we'd better care older kernel too, because relay will be
replaced by new unified trace buffer.
What about checking free memory by using si_meminfo()?

-- 


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

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-11-10 19:25 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-11-10 17:11 [Bug runtime/7016] New: Systemtap will causes OOM when specifying large relay buffer size mhiramat at redhat dot com
2008-11-10 17:14 ` [Bug runtime/7016] " mhiramat at redhat dot com
2008-11-10 18:42 ` fche at redhat dot com
2008-11-10 19:25 ` mhiramat at redhat dot com

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).