From: Ingo Molnar <mingo@elte.hu>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/2] vsprintf: introduce %pT format specifier
Date: Wed, 23 Mar 2011 14:12:13 +0100 [thread overview]
Message-ID: <20110323131213.GA25467@elte.hu> (raw)
In-Reply-To: <1300884395-13835-1-git-send-email-namhyung@gmail.com>
* Namhyung Kim <namhyung@gmail.com> wrote:
> The %pT format specifier is for stack backtrace. Its handler
> sprint_trace() does symbol lookup using (address-1) to ensure
> the address will not point outside of the function.
>
> If there is a tail-call to the function marked "noreturn",
> gcc optimized out the code after the call then causes saved
> return address points outside of the function (i.e. the start
> of the next function), so pollutes call trace somewhat.
> This patch will fix it.
>
> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
> Cc: linux-arch@vger.kernel.org
> ---
> include/linux/kallsyms.h | 7 +++++++
> kernel/kallsyms.c | 40 ++++++++++++++++++++++++++++++++++++++++
> lib/vsprintf.c | 7 ++++++-
> 3 files changed, 53 insertions(+), 1 deletions(-)
Looks useful. Please include before/after stack dump examples in the changelog,
to show the difference.
Thanks,
Ingo
next prev parent reply other threads:[~2011-03-23 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 12:46 [PATCH 1/2] vsprintf: introduce %pT format specifier Namhyung Kim
2011-03-23 13:12 ` Ingo Molnar [this message]
2011-03-23 13:29 ` [PATCH RESEND " Namhyung Kim
2011-03-23 13:43 ` Steven Rostedt
2011-03-23 13:49 ` Frederic Weisbecker
2011-03-23 13:49 ` Frederic Weisbecker
2011-03-23 14:16 ` Ingo Molnar
2011-03-23 14:16 ` Ingo Molnar
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=20110323131213.GA25467@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=rostedt@goodmis.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 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).