From: Catalin Marinas <catalin.marinas@arm.com>
To: Joe Perches <joe@perches.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] kmemleak: use pr_fmt
Date: Mon, 22 Jun 2009 10:55:52 +0100 [thread overview]
Message-ID: <1245664552.15580.36.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <1245440992.6201.17.camel@Joe-Laptop>
On Fri, 2009-06-19 at 12:49 -0700, Joe Perches wrote:
> On Fri, 2009-06-19 at 10:53 +0100, Catalin Marinas wrote:
> > Thanks for the patch. It missed one pr_info case (actually invoked via
> > the pr_helper macro).
>
> This change will affect the seq_printf uses.
> Some think the seq output should be immutable.
> Perhaps that's important to you or others.
My point was that with your patch, the kmemleak kernel messages with
pr_info were something like:
kmemleak: kmemleak: unreferenced object ...
kmemleak: comm ...
kmemleak: backtrace:
After dropping "kmemleak: " in the print_helper() call, kernel messages
become (which I find nicer):
kmemleak: unreferenced object ...
kmemleak: comm ...
kmemleak: backtrace:
For the seq_printf() we really don't need the "kmemleak: " prefix since
you read a kmemleak-specific file anyway. With my modification, the seq
output becomes:
unreferenced object ...
comm ...
backtrace:
i.e. without the "kmemleak: " prefix on the "unreferenced ..." line.
--
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>
prev parent reply other threads:[~2009-06-22 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 16:08 [PATCH] kmemleak: use pr_fmt Joe Perches
2009-06-19 9:53 ` Catalin Marinas
2009-06-19 19:49 ` Joe Perches
2009-06-22 9:55 ` Catalin Marinas [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=1245664552.15580.36.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@cs.helsinki.fi \
/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;
as well as URLs for NNTP newsgroup(s).