All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Olaf Hering <olaf@aepfle.de>, xen-devel@lists.xen.org
Subject: Re: identify a Xen PV domU to fix devmem_is_allowed
Date: Tue, 1 Mar 2016 15:29:29 +0000	[thread overview]
Message-ID: <56D5B559.8000306@citrix.com> (raw)
In-Reply-To: <20160229102849.GA18202@aepfle.de>

On 29/02/16 10:28, Olaf Hering wrote:
> What is the correct way to identify a Xen PV domU in the kenrel?
> devmem_is_allowed() used to disable access to pages < 256 in domU.
> With pvops this check was removed, or never ported forward.
> 
> Would this change be the correct fix?

I think the bug is in range_is_allowed() as it is using
devmem_is_allowed() to avoid having to correctly check for aliases.

David

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      parent reply	other threads:[~2016-03-01 15:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 10:28 identify a Xen PV domU to fix devmem_is_allowed Olaf Hering
2016-02-29 15:10 ` Konrad Rzeszutek Wilk
2016-02-29 15:29   ` Olaf Hering
2016-02-29 18:32     ` Boris Ostrovsky
2016-03-01 15:14       ` Olaf Hering
2016-03-01 10:38   ` Jan Beulich
2016-03-01 14:34     ` Konrad Rzeszutek Wilk
2016-03-01 14:45       ` Boris Ostrovsky
2016-03-15 16:57         ` Olaf Hering
2016-03-15 18:56           ` Boris Ostrovsky
2016-03-21 21:29           ` Boris Ostrovsky
2016-03-22 18:37             ` Boris Ostrovsky
2016-03-23  8:28               ` Olaf Hering
2016-06-06 21:17               ` Olaf Hering
2016-03-01 16:23   ` Olaf Hering
2016-03-01 15:29 ` David Vrabel [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=56D5B559.8000306@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=olaf@aepfle.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.