From: Pekka Enberg <penberg@cs.helsinki.fi>
To: David Rientjes <rientjes@google.com>
Cc: "Catalin Marinas" <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org,
"Toralf Förster" <toralf.foerster@gmx.de>,
"Ted Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH] kmemleak: Reduce verbosity when memory allocation fails
Date: Wed, 12 Jan 2011 08:59:26 +0200 [thread overview]
Message-ID: <4D2D514E.5090308@cs.helsinki.fi> (raw)
In-Reply-To: <alpine.DEB.2.00.1101111332330.7551@chino.kir.corp.google.com>
On 1/11/11 11:34 PM, David Rientjes wrote:
> On Tue, 11 Jan 2011, Catalin Marinas wrote:
>
>> kmemleak: Allow kmemleak metadata allocations to fail
>>
>> From: Catalin Marinas<catalin.marinas@arm.com>
>>
>> This patch adds __GFP_NORETRY and __GFP_NOMEMALLOC flags to the kmemleak
>> metadata allocations so that it has a smaller effect on the users of the
>> kernel slab allocator. Since kmemleak allocations can now fail more
>> often, this patch also reduces the verbosity by passing __GFP_NOWARN and
>> not dumping the stack trace when a kmemleak allocation fails.
>>
>> Signed-off-by: Catalin Marinas<catalin.marinas@arm.com>
>> Reported-by: Toralf Förster<toralf.foerster@gmx.de>
>> Cc: Pekka Enberg<penberg@cs.helsinki.fi>
>> Cc: David Rientjes<rientjes@google.com>
>> Cc: Ted Ts'o<tytso@mit.edu>
>
> Acked-by: David Rientjes<rientjes@google.com>
Acked-by: Pekka Enberg <penberg@kernel.org>
prev parent reply other threads:[~2011-01-12 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 18:11 [PATCH] kmemleak: Reduce verbosity when memory allocation fails Catalin Marinas
2011-01-10 20:36 ` David Rientjes
2011-01-10 22:00 ` Catalin Marinas
2011-01-10 23:31 ` David Rientjes
2011-01-11 12:44 ` Catalin Marinas
2011-01-11 21:34 ` David Rientjes
2011-01-12 6:59 ` Pekka Enberg [this message]
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=4D2D514E.5090308@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=toralf.foerster@gmx.de \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox