From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
Tim Deegan <tim@xen.org>
Subject: [Patch v4 0/4] Xen stack trace printing improvements
Date: Wed, 20 Nov 2013 13:09:38 +0000 [thread overview]
Message-ID: <1384952982-1490-1-git-send-email-andrew.cooper3@citrix.com> (raw)
This series consists of improvements to Xen's ability to print traces of its
own stack, and specifically for the stack overflow case to be able to use
frame pointers in a debug build.
v4 contains some fixes to the wild function pointer call case, including a
test case. There was a missed indirection in the test, and when printing the
return address.
I have dev tested the series in debug and non-debug cases, with and without
memory guards, and I believe that all the stack traces look correct (given the
available information Xen has), and that the boundaries are now correct. This
series has had a substantial rebase on top of the %pS series.
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>
CC: George Dunlap <george.dunlap@eu.citrix.com>
next reply other threads:[~2013-11-20 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 13:09 Andrew Cooper [this message]
2013-11-20 13:09 ` [Patch v4 1/4] x86/stack: Refactor show_trace() Andrew Cooper
2013-11-20 13:40 ` Jan Beulich
2013-11-20 14:11 ` Andrew Cooper
2013-11-20 14:22 ` Jan Beulich
2013-11-20 14:30 ` [Patch v5 " Andrew Cooper
2013-11-20 13:09 ` [Patch v4 2/4] x86/stack: Adjust boundary conditions for printed stacks Andrew Cooper
2013-11-20 13:09 ` [Patch v4 3/4] x86/stack: Change show_stack_overflow() to use frame pointers if available Andrew Cooper
2013-11-20 13:09 ` [Patch v4 4/4] DO NOT APPLY: Test code for interesting stack overflows Andrew Cooper
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=1384952982-1490-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=george.dunlap@eu.citrix.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).