Subject : Found the commit that causes the OOMs
Submitter : David Howells <firstname.lastname@example.org>
Date : 2009-06-27 08:12
References : http://lkml.org/lkml/2009/6/27/28
Handled-By : Wu Fengguang <email@example.com>
Patch : http://patchwork.kernel.org/patch/32740/
This entry is being used for tracking a regression from 2.6.30. Please don't
close it until the problem is fixed in the mainline.
Author: MinChan Kim <firstname.lastname@example.org>
Date: Tue Jun 16 15:32:44 2009 -0700
vmscan: prevent shrinking of active anon lru list in case of no swap space V3
First-Bad-Commit : 69c854817566db82c362797b4a6521d0b00fe1d8
On Tuesday 07 July 2009, Minchan Kim wrote:
> On Tue, 7 Jul 2009 02:01:03 +0200 (CEST)
> "Rafael J. Wysocki" <email@example.com> wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > The following bug entry is on the current list of known regressions
> > from 2.6.30. Please verify if it still should be listed and let me know
> > (either way).
> It should be listed.
> I think it is caused by forking process bomb by msgctl11 on LTP.
> We can refer old
> I think this issue can be solved by
> dynamic reclaim throttling patch which is making by Rik.
> After he merges it, Let's test again.
Patch : http://lkml.org/lkml/2009/7/7/104
On Tuesday 28 July 2009, Andrew Morton wrote:
> (cc Rafael)
> On Tue, 28 Jul 2009 09:07:18 +0900 (JST) KOSAKI Motohiro
> <firstname.lastname@example.org> wrote:
> > >
> > > hm, what ended up happening here?
> > >
> > > Thanks.
> > 1) This is NOT regression. the test-case can't run on 1GB machine.
> > sometimes run successful, another sometimes run failure...
> > (in later mail, David said old kernel also cause OOM on his machine)
> > 2) However, Rik's patch dramatically reduce OOM risk on this workload.
> > The last remain problem is:
> > if highmem is used file caches, userland stack might allocate normal-zone.
> > it can cause OOM.
> > but it is definitely another issue.
> > dropcache before running msgctl11 solve this issue.
> > Conclusion: I agree this bug can be closed.