From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
Tim Deegan <tim@xen.org>
Subject: [Patch v3 1/4] x86/stack: Refactor show_trace()
Date: Mon, 18 Nov 2013 19:34:21 +0000 [thread overview]
Message-ID: <1384803264-1093-2-git-send-email-andrew.cooper3@citrix.com> (raw)
In-Reply-To: <1384803264-1093-1-git-send-email-andrew.cooper3@citrix.com>
Before, show_trace() had two implementations depending on
CONFIG_FRAME_POINTER. Some parts were common, while the loops to wander up
the stack were different.
The version aided by frame pointers had a special case for function calls on
wild function pointers, but this doesn't need to be a special case.
After the refactoring, there are now two implementations of __show_trace()
which differ depending on CONFIG_FRAME_POINTER, and a single show_trace()
with the common bits, including the logic for wild function pointers.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
CC: Keir Fraser <keir@xen.org>
CC: Jan Beulich <JBeulich@suse.com>
CC: Tim Deegan <tim@xen.org>
---
xen/arch/x86/traps.c | 65 +++++++++++++++++++++++++++++++-------------------
1 file changed, 41 insertions(+), 24 deletions(-)
diff --git a/xen/arch/x86/traps.c b/xen/arch/x86/traps.c
index e5b3585..5917291 100644
--- a/xen/arch/x86/traps.c
+++ b/xen/arch/x86/traps.c
@@ -195,12 +195,14 @@ static void show_guest_stack(struct vcpu *v, struct cpu_user_regs *regs)
#if !defined(CONFIG_FRAME_POINTER)
-static void show_trace(struct cpu_user_regs *regs)
+/*
+ * Stack trace from pointers found in stack, unaided by frame pointers. For
+ * caller convenience, this has the same prototype as its alternative, and
+ * simply ignores the base pointer parameter.
+ */
+static void __show_trace(unsigned long sp, unsigned long __maybe_unused bp)
{
- unsigned long *stack = ESP_BEFORE_EXCEPTION(regs), addr;
-
- printk("Xen call trace:\n"
- " [<%p>] %pS\n", _p(regs->eip), _p(regs->eip));
+ unsigned long *stack = (unsigned long *)sp, addr;
while ( ((long)stack & (STACK_SIZE-BYTES_PER_LONG)) != 0 )
{
@@ -208,35 +210,22 @@ static void show_trace(struct cpu_user_regs *regs)
if ( is_active_kernel_text(addr) )
printk(" [<%p>] %pS\n", _p(addr), _p(addr));
}
-
- printk("\n");
}
#else
-static void show_trace(struct cpu_user_regs *regs)
+/* Stack trace from frames in the stack, using frame pointers */
+static void __show_trace(unsigned long sp, unsigned long bp)
{
unsigned long *frame, next, addr, low, high;
- /*
- * If RIP is not pointing into hypervisor code then someone may have
- * called into oblivion. Peek to see if they left a return address at
- * top of stack.
- */
- addr = is_active_kernel_text(regs->eip) ||
- !is_active_kernel_text(*ESP_BEFORE_EXCEPTION(regs)) ?
- regs->eip : *ESP_BEFORE_EXCEPTION(regs);
-
- printk("Xen call trace:\n"
- " [<%p>] %pS\n", _p(addr), _p(addr));
-
/* Bounds for range of valid frame pointer. */
- low = (unsigned long)(ESP_BEFORE_EXCEPTION(regs) - 2);
+ low = sp - 2*sizeof(unsigned long);
high = (low & ~(STACK_SIZE - 1)) +
(STACK_SIZE - sizeof(struct cpu_info) - 2*sizeof(unsigned long));
/* The initial frame pointer. */
- next = regs->ebp;
+ next = bp;
for ( ; ; )
{
@@ -268,12 +257,40 @@ static void show_trace(struct cpu_user_regs *regs)
low = (unsigned long)&frame[2];
}
-
- printk("\n");
}
#endif
+static void show_trace(const struct cpu_user_regs *regs)
+{
+ unsigned long sp = regs->rsp;
+
+ printk("Xen call trace:\n");
+
+ /*
+ * If RIP looks sensible, or the top of the stack doesn't, print RIP at
+ * the top of the stack trace.
+ */
+ if ( is_active_kernel_text(regs->rip) ||
+ !is_active_kernel_text(regs->rsp) )
+ printk(" [<%p>] %pS\n", _p(regs->eip), _p(regs->eip));
+ /*
+ * else RIP looks bad but the top of the stack looks good. Perhaps we
+ * followed a wild function pointer? Lets assume the top of the stack is a
+ * return address; print it and skip past so __show_trace() doesn't print
+ * it again.
+ */
+ else
+ {
+ printk(" [<%p>] %pS\n", _p(sp), _p(sp));
+ sp += sizeof (unsigned long);
+ }
+
+ __show_trace(sp, regs->rbp);
+
+ printk("\n");
+}
+
void show_stack(struct cpu_user_regs *regs)
{
unsigned long *stack = ESP_BEFORE_EXCEPTION(regs), addr;
--
1.7.10.4
next prev parent reply other threads:[~2013-11-18 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 19:34 [Patch v3 0/4] Xen stack trace printing improvements Andrew Cooper
2013-11-18 19:34 ` Andrew Cooper [this message]
2013-11-20 9:43 ` [Patch v3 1/4] x86/stack: Refactor show_trace() Jan Beulich
2013-11-18 19:34 ` [Patch v3 2/4] x86/stack: Adjust boundary conditions for printed stacks Andrew Cooper
2013-11-20 9:49 ` Jan Beulich
2013-11-18 19:34 ` [Patch v3 3/4] x86/stack: Change show_stack_overflow() to use frame pointers if available Andrew Cooper
2013-11-20 9:51 ` Jan Beulich
2013-11-18 19:34 ` [Patch v3 4/4] DO NOT APPLY: Test code for interesting stack overflows Andrew Cooper
2013-11-19 10:10 ` [Patch v3 0/4] Xen stack trace printing improvements George Dunlap
2013-11-19 10:50 ` Andrew Cooper
2013-11-19 11:01 ` George Dunlap
2013-11-19 16:07 ` Keir Fraser
2013-11-19 16:10 ` Jan Beulich
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=1384803264-1093-2-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).