From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Jonathan Woithe <jwoithe@atrad.com.au>
Cc: David Rientjes <rientjes@google.com>, linux-mm@kvack.org
Subject: Re: OOM triggered with plenty of memory free
Date: Wed, 13 Feb 2013 07:14:50 -0800 [thread overview]
Message-ID: <511BADEA.3070403@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130213042552.GC32135@marvin.atrad.com.au>
On 02/12/2013 08:25 PM, Jonathan Woithe wrote:
>> > Better yet would be to try to upgrade these machines to a more recent
>> > kernel to see if it is already fixed. Are we allowed to upgrade or at
>> > least enable kmemleak?
> Upgrading to a recent kernel would be a possibility if it was proven to fix
> the problem; doing it "just to check" will be impossible I fear, at least on
> the production systems. Enabling KMEMLEAK on 2.6.35.x may be doable.
>
> I will see whether I can gain access to a test system and if so, try a more
> recent kernel to see if it makes any difference.
>
> I'll advise which of these options proves practical as soon as possible and
> report any findings which come out of them.
Are there any non-upstream bits in the kernel? Any third-party drivers
or filesystems?
David's analysis looks spot-on. The only other thing I'll add is that
it just looks weird that all three kmalloc() caches are so _even_:
>> kmalloc-128 1234556 1235168 128 32 1 : tunables 0 0 0 : slabdata 38599 38599 0
>> kmalloc-64 1238117 1238144 64 64 1 : tunables 0 0 0 : slabdata 19346 19346 0
>> kmalloc-32 1236600 1236608 32 128 1 : tunables 0 0 0 : slabdata 9661 9661 0
It's almost like something goes and does 3 allocations in series and
leaks them all.
There are also quite a few buffer_heads:
> buffer_head 496273 640794 56 73 1 : tunables 0 0 0 : slabdata 8778 8778 0
which seem out-of-whack for the small amount of memory being used for
I/O-related stuff. That kinda points in the direction of I/O or
filesystems.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-02-13 15:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 3:10 OOM triggered with plenty of memory free Jonathan Woithe
2013-02-13 3:30 ` David Rientjes
2013-02-13 4:25 ` Jonathan Woithe
2013-02-13 15:14 ` Dave Hansen [this message]
2013-02-13 22:49 ` Jonathan Woithe
2013-02-21 6:01 ` Jonathan Woithe
2013-02-26 6:39 ` Jonathan Woithe
2013-02-26 15:26 ` Dave Hansen
2013-02-26 20:54 ` Eric W. Biederman
2013-03-04 5:25 ` Jonathan Woithe
2013-02-20 5:50 ` Simon Jeons
2013-02-20 7:05 ` David Rientjes
-- strict thread matches above, loose matches on Subject: below --
2013-03-16 9:25 Hillf Danton
2013-03-16 9:25 ` Hillf Danton
2013-03-16 9:33 ` Raymond Jennings
2013-03-16 9:33 ` Raymond Jennings
2013-03-16 11:02 ` Jonathan Woithe
2013-03-16 11:02 ` Jonathan Woithe
2013-03-20 5:47 ` Jonathan Woithe
2013-03-20 5:47 ` Jonathan Woithe
2013-03-21 7:07 ` Jonathan Woithe
2013-03-21 7:07 ` Jonathan Woithe
2013-03-25 2:24 ` Jonathan Woithe
2013-03-25 2:24 ` Jonathan Woithe
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=511BADEA.3070403@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=jwoithe@atrad.com.au \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.