From: "Jan Beulich" <JBeulich@suse.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: [PATCH 0/2]: x86/traps: improve show_trace()'s top-of-stack handling
Date: Fri, 31 May 2019 02:59:20 -0600 [thread overview]
Message-ID: <5CF0ECE80200007800233D41@prv1-mh.provo.novell.com> (raw)
1: guard top-of-stack reads
2: widen condition for logging top-of-stack
The issue patch 2 fixes (a curious lack of an intermediate call stack
entry) was observed in practice; patch 1 is a result of me just looking
at the code (and if I have missed some aspect of why this isn't a
problem in reality, that patch could be easily dropped).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich@suse.com>
To: "xen-devel" <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH 0/2]: x86/traps: improve show_trace()'s top-of-stack handling
Date: Fri, 31 May 2019 02:59:20 -0600 [thread overview]
Message-ID: <5CF0ECE80200007800233D41@prv1-mh.provo.novell.com> (raw)
Message-ID: <20190531085920.GD9fMZfggl96vAO6gTCNha0w_6Ovze3pqxhRB_Aufsc@z> (raw)
1: guard top-of-stack reads
2: widen condition for logging top-of-stack
The issue patch 2 fixes (a curious lack of an intermediate call stack
entry) was observed in practice; patch 1 is a result of me just looking
at the code (and if I have missed some aspect of why this isn't a
problem in reality, that patch could be easily dropped).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-05-31 8:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 8:59 Jan Beulich [this message]
2019-05-31 8:59 ` [Xen-devel] [PATCH 0/2]: x86/traps: improve show_trace()'s top-of-stack handling Jan Beulich
2019-05-31 9:17 ` [PATCH 1/2] x86/traps: guard top-of-stack reads Jan Beulich
2019-05-31 9:17 ` [Xen-devel] " Jan Beulich
2019-06-07 17:51 ` Andrew Cooper
2019-06-11 9:57 ` Jan Beulich
2019-05-31 9:22 ` [PATCH 2/2] x86/traps: widen condition for logging top-of-stack Jan Beulich
2019-05-31 9:22 ` [Xen-devel] " Jan Beulich
2019-06-07 18:01 ` Andrew Cooper
2019-06-11 9:46 ` Jan Beulich
2019-06-17 8:10 ` [Xen-devel] [PATCH v2 0/2]: x86/traps: improve show_trace()'s top-of-stack handling Jan Beulich
2019-06-17 8:12 ` [Xen-devel] [PATCH v2 1/2] x86/traps: guard top-of-stack reads Jan Beulich
2019-07-02 17:47 ` Andrew Cooper
2019-07-03 7:10 ` Jan Beulich
2019-06-17 8:13 ` [Xen-devel] [PATCH v2 2/2] x86/traps: widen condition for logging top-of-stack Jan Beulich
2019-07-03 10:21 ` Andrew Cooper
2019-07-03 10:34 ` Jan Beulich
2019-07-03 19:47 ` Andrew Cooper
2019-07-04 9:09 ` 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=5CF0ECE80200007800233D41@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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).