[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+55aFy2zh0BHvNYfUXvOaWWvagrKDrFy4DvTtPNjO7nS2G9Tw@mail.gmail.com>
Date: Sat, 14 Apr 2012 14:03:08 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: werner <w.landgraf@...ru>
Cc: David Rientjes <rientjes@...gle.com>,
Colin Cross <ccross@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>,
Hugh Dickins <hughd@...gle.com>, linux-kernel@...r.kernel.org,
Oleg Nesterov <oleg@...hat.com>,
Rabin Vincent <rabin.vincent@...ricsson.com>,
Christian Bejram <christian.bejram@...ricsson.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Anton Vorontsov <anton.vorontsov@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
stable@...r.kernel.org
Subject: Re: v3.4-rc2 out-of-memory problems (was Re: 3.4-rc1 sticks-and-crashs)
On Sat, Apr 14, 2012 at 12:38 PM, werner <w.landgraf@...ru> wrote:
>
> I observed that then always kmemleak is almost at the beginning of top
Just disable CONFIG_DEBUG_KMEMLEAK.
You do realize that it's a pure debugging aid - akin to
CONFIG_DEBUG_PAGEALLOC - that is *not* meant to be run on production
systems. Exactly because it is very expensive. It basically scans all
the kernel areas for pointers and tries to find leaks.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists