From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Soren Sandmann <ssp@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Robert Richter <robert.richter@amd.com>
Subject: Re: [PATCH RESEND v5 -tip] x86, dumpstack: Correct stack dump info when frame pointer is available
Date: Fri, 18 Mar 2011 10:40:33 +0100 [thread overview]
Message-ID: <1300441233.21794.32.camel@twins> (raw)
In-Reply-To: <1300416006-3163-1-git-send-email-namhyung@gmail.com>
On Fri, 2011-03-18 at 11:40 +0900, Namhyung Kim wrote:
>
> Current stack dump code scans entire stack and check each entry
> contains a pointer to kernel code. If CONFIG_FRAME_POINTER=y it
> could mark whether the pointer is valid or not based on value of
> the frame pointer. Invalid entries could be preceded by '?' sign.
>
> However this was not going to happen because scan start point was
> always higher than the frame pointer so that they could not meet.
>
> Commit 9c0729dc8062 ("x86: Eliminate bp argument from the stack
> tracing routines") delayed bp acquisition point, so the bp was
> read in lower frame, thus all of the entries were marked invalid.
>
> This patch fixes this by reverting above commit while retaining
> stack_frame() helper as suggested by Frederic Weisbecker.
> End result looks like below:
>
> before:
> [ 3.508329] Call Trace:
> [ 3.508551] [<ffffffff814f35c9>] ? panic+0x91/0x199
> [ 3.508662] [<ffffffff814f3739>] ? printk+0x68/0x6a
> [ 3.508770] [<ffffffff81a981b2>] ? mount_block_root+0x257/0x26e
> [ 3.508876] [<ffffffff81a9821f>] ? mount_root+0x56/0x5a
> [ 3.508975] [<ffffffff81a98393>] ? prepare_namespace+0x170/0x1a9
> [ 3.509216] [<ffffffff81a9772b>] ? kernel_init+0x1d2/0x1e2
> [ 3.509335] [<ffffffff81003894>] ? kernel_thread_helper+0x4/0x10
> [ 3.509442] [<ffffffff814f6880>] ? restore_args+0x0/0x30
> [ 3.509542] [<ffffffff81a97559>] ? kernel_init+0x0/0x1e2
> [ 3.509641] [<ffffffff81003890>] ? kernel_thread_helper+0x0/0x10
>
> after:
> [ 3.522991] Call Trace:
> [ 3.523351] [<ffffffff814f35b9>] panic+0x91/0x199
> [ 3.523468] [<ffffffff814f3729>] ? printk+0x68/0x6a
> [ 3.523576] [<ffffffff81a981b2>] mount_block_root+0x257/0x26e
> [ 3.523681] [<ffffffff81a9821f>] mount_root+0x56/0x5a
> [ 3.523780] [<ffffffff81a98393>] prepare_namespace+0x170/0x1a9
> [ 3.523885] [<ffffffff81a9772b>] kernel_init+0x1d2/0x1e2
> [ 3.523987] [<ffffffff81003894>] kernel_thread_helper+0x4/0x10
> [ 3.524228] [<ffffffff814f6880>] ? restore_args+0x0/0x30
> [ 3.524345] [<ffffffff81a97559>] ? kernel_init+0x0/0x1e2
> [ 3.524445] [<ffffffff81003890>] ? kernel_thread_helper+0x0/0x10
>
> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Soren Sandmann <ssp@redhat.com>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Paul Mackerras <paulus@samba.org>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Robert Richter <robert.richter@amd.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Ingo, _please_, pretty _please_ merge this? These wrecked unwinds drive
me up the wall ;-)
next prev parent reply other threads:[~2011-03-18 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 2:40 [PATCH RESEND v5 -tip] x86, dumpstack: Correct stack dump info when frame pointer is available Namhyung Kim
2011-03-18 9:40 ` Peter Zijlstra [this message]
2011-03-18 12:47 ` [tip:x86/urgent] " tip-bot for Namhyung Kim
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=1300441233.21794.32.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=robert.richter@amd.com \
--cc=ssp@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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