Bug 457411 - box OOM's under heavy mmap usage.
Summary: box OOM's under heavy mmap usage.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.2
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Rik van Riel
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-31 14:52 UTC by Josef Bacik
Modified: 2011-08-07 12:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-07 12:44:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
reproducer (11.94 MB, application/octet-stream)
2008-07-31 14:52 UTC, Josef Bacik 		no flags Details
oom messages (5.10 KB, text/plain)
2008-07-31 14:53 UTC, Josef Bacik 		no flags Details
View All

Description Josef Bacik 2008-07-31 14:52:46 UTC 
While investigating a locking order bug that resulted in a hang (bz 439548) it
was discovered that when the locking bug was fixed and the testcase was able to
continue that it would cause an OOM kill.  This problem is reproduceable upstream.

The testcase is simple, untar it, edit the VAR file to point at a blank
partition/volume that it will use, and then do sh run.sh and it will start, at
some point you will see things getting killed.  I'm also attaching a txt file
with a sample of the OOM messages I got (on an upstream kernel).
Comment 1 Josef Bacik 2008-07-31 14:52:48 UTC 
Created attachment 313105 [details]
reproducer
Comment 2 Josef Bacik 2008-07-31 14:53:23 UTC 
Created attachment 313106 [details]
oom messages
Comment 4 Rik van Riel 2010-11-19 22:11:20 UTC 
I did look at it.  I fixed it for RHEL 6 with the split LRU code.

I'm not entirely convinced it is fixable for RHEL 5, though if I come up with an idea one day I'd like to :)
Comment 5 Ronen Hod 2011-08-07 12:44:59 UTC 
Too old for RHEL5.8.
Closing.
Note You need to log in before you can comment on or make changes to this bug.