From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir@xen.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0/5] x86: properly propagate errors to hypercall callee
Date: Tue, 15 Mar 2011 12:29:07 +0000 [thread overview]
Message-ID: <4D7F69A30200007800036914@vpn.id2.novell.com> (raw)
In-Reply-To: <4D776A320200007800035752@vpn.id2.novell.com>
>>> On 09.03.11 at 11:53, "Jan Beulich" <JBeulich@novell.com> wrote:
> 1: don't BUG() post-boot in alloc_xen_pagetable()
> 2: run-time callers of map_pages_to_xen() must check for errors
I actually think that the first two should be considered for 4.0 and
4.1, as those are preventing a guest induced host crash. The other
three are more of enhancement type (propagating a meaningful
error to the calling guest).
Jan
> 3: make get_page_from_l1e() return a proper error code
> 4: make mod_l1_entry() return a proper error code
> 5: make mod_l2_entry() return a proper error code
>
> All but the last are clear candidates for backporting to 4.1 and 4.0,
> albeit for the former perhaps only after 4.1.0.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
prev parent reply other threads:[~2011-03-15 12:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 10:53 [PATCH 0/5] x86: properly propagate errors to hypercall callee Jan Beulich
2011-03-09 11:07 ` Keir Fraser
2011-03-09 11:21 ` Jan Beulich
2011-03-09 13:44 ` Keir Fraser
2011-03-09 14:20 ` Jan Beulich
2011-03-09 15:10 ` Konrad Rzeszutek Wilk
2011-03-09 15:40 ` Jan Beulich
2011-03-11 9:25 ` Jan Beulich
2011-03-11 9:45 ` Keir Fraser
2011-03-11 10:44 ` Jan Beulich
2011-03-11 12:33 ` Keir Fraser
2011-03-15 12:29 ` Jan Beulich [this message]
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=4D7F69A30200007800036914@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.com \
/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).