From: George Dunlap <george.dunlap@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Julien Grall <julien.grall@arm.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH 1/3] x86: replace bad ASSERT() in xenmem_add_to_physmap_one()
Date: Mon, 27 Nov 2017 14:08:31 +0000 [thread overview]
Message-ID: <aabda94c-d9fd-0b05-c3ec-19ac2b51fa2e@citrix.com> (raw)
In-Reply-To: <5A1BE4C00200007800192332@prv-mh.provo.novell.com>
On 11/27/2017 09:11 AM, Jan Beulich wrote:
> There are no locks being held, i.e. it is possible to be triggered by
> racy hypercall invocations. Subsequent code doesn't really depend on the
> checked values, so this is not a security issue.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: George Dunlap <george.dunlap@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2017-11-27 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 8:34 [PATCH 0/3] XENMEM_add_to_physmap handling adjustments Jan Beulich
2017-11-27 9:11 ` [PATCH 1/3] x86: replace bad ASSERT() in xenmem_add_to_physmap_one() Jan Beulich
2017-11-27 11:39 ` Andrew Cooper
2017-11-27 14:08 ` George Dunlap [this message]
2017-11-27 9:12 ` [PATCH 2/3] x86: check paging mode earlier " Jan Beulich
2017-11-27 11:07 ` George Dunlap
2017-11-27 11:40 ` Andrew Cooper
2017-11-27 9:12 ` [PATCH 3/3] improve XENMEM_add_to_physmap_batch address checking Jan Beulich
2017-11-27 11:41 ` Andrew Cooper
2017-11-27 12:16 ` [PATCH 0/3] XENMEM_add_to_physmap handling adjustments Julien Grall
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=aabda94c-d9fd-0b05-c3ec-19ac2b51fa2e@citrix.com \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--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).