From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: Recent 3.x kernels: Memory leak causing OOMs
Date: Mon, 17 Feb 2014 18:34:28 +0000 [thread overview]
Message-ID: <20140217183428.GA8687@arm.com> (raw)
In-Reply-To: <20140216214354.GA12947@thunk.org>
On Sun, Feb 16, 2014 at 04:43:54PM -0500, Theodore Ts'o wrote:
> On Sun, Feb 16, 2014 at 08:05:04PM +0000, Russell King - ARM Linux wrote:
> > I have another machine which OOM'd a week ago with plenty of unused swap
> > - it uses ext3 on raid1 and is a more busy system. That took 41 days
> > to show, and upon reboot, it got a kernel with kmemleak enabled. So far,
> > after 7 days, kmemleak has found nothing at all.
>
> If kmemleak doesn't show anything, then presumably it's not a leak of
> the slab object. Does /proc/meminfo show anything interesting? Maybe
> it's a page getting leaked (which wouldn't be noticed by kmemleak)
Kmemleak also doesn't notice leaked objects that are added to a list for
example (still referenced). Maybe /proc/slabinfo would give some clues.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Recent 3.x kernels: Memory leak causing OOMs
Date: Mon, 17 Feb 2014 18:34:28 +0000 [thread overview]
Message-ID: <20140217183428.GA8687@arm.com> (raw)
In-Reply-To: <20140216214354.GA12947@thunk.org>
On Sun, Feb 16, 2014 at 04:43:54PM -0500, Theodore Ts'o wrote:
> On Sun, Feb 16, 2014 at 08:05:04PM +0000, Russell King - ARM Linux wrote:
> > I have another machine which OOM'd a week ago with plenty of unused swap
> > - it uses ext3 on raid1 and is a more busy system. That took 41 days
> > to show, and upon reboot, it got a kernel with kmemleak enabled. So far,
> > after 7 days, kmemleak has found nothing at all.
>
> If kmemleak doesn't show anything, then presumably it's not a leak of
> the slab object. Does /proc/meminfo show anything interesting? Maybe
> it's a page getting leaked (which wouldn't be noticed by kmemleak)
Kmemleak also doesn't notice leaked objects that are added to a list for
example (still referenced). Maybe /proc/slabinfo would give some clues.
--
Catalin
--
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:[~2014-02-17 18:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 20:05 Recent 3.x kernels: Memory leak causing OOMs Russell King - ARM Linux
2014-02-16 20:05 ` Russell King - ARM Linux
2014-02-16 21:43 ` Theodore Ts'o
2014-02-16 21:43 ` Theodore Ts'o
2014-02-17 18:34 ` Catalin Marinas [this message]
2014-02-17 18:34 ` Catalin Marinas
2014-02-16 22:17 ` David Rientjes
2014-02-16 22:17 ` David Rientjes
2014-02-16 22:50 ` Russell King - ARM Linux
2014-02-16 22:50 ` Russell King - ARM Linux
2014-02-16 23:42 ` David Rientjes
2014-02-16 23:42 ` David Rientjes
2014-02-17 21:02 ` Maxime Bizon
2014-02-17 21:02 ` Maxime Bizon
2014-02-17 21:09 ` Russell King - ARM Linux
2014-02-17 21:09 ` Russell King - ARM Linux
2014-03-15 10:19 ` Russell King - ARM Linux
2014-03-15 10:19 ` Russell King - ARM Linux
2014-03-17 7:07 ` NeilBrown
2014-03-17 7:07 ` NeilBrown
2014-03-17 8:51 ` Russell King - ARM Linux
2014-03-17 8:51 ` Russell King - ARM Linux
2014-03-17 8:51 ` Russell King - ARM Linux
2014-03-17 18:18 ` Catalin Marinas
2014-03-17 18:18 ` Catalin Marinas
2014-03-17 19:33 ` Russell King - ARM Linux
2014-03-17 19:33 ` Russell King - ARM Linux
2014-04-01 9:19 ` Russell King - ARM Linux
2014-04-01 9:19 ` Russell King - ARM Linux
2014-04-01 11:38 ` Russell King - ARM Linux
2014-04-01 11:38 ` Russell King - ARM Linux
2014-04-01 14:04 ` Russell King - ARM Linux
2014-04-01 14:04 ` Russell King - ARM Linux
2014-04-02 23:28 ` NeilBrown
2014-04-02 23:28 ` NeilBrown
2014-04-01 15:58 ` Catalin Marinas
2014-04-01 15:58 ` Catalin Marinas
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=20140217183428.GA8687@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.