public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Julien Grall <julien.grall@arm.com>, <boris.ostrovsky@oracle.com>,
	<david.vrabel@citrix.com>, <jgross@suse.com>,
	<sstabellini@kernel.org>, <konrad.wilk@oracle.com>
Cc: <steve.capper@arm.com>, <andrew.cooper3@citrix.com>,
	<linux-kernel@vger.kernel.org>, <xen-devel@lists.xen.org>,
	<JBeulich@suse.com>
Subject: Re: [Xen-devel] [PATCH] xen: grant-table: Check truncation when giving access to a frame
Date: Mon, 13 Jun 2016 11:57:28 +0100	[thread overview]
Message-ID: <575E9198.70103@citrix.com> (raw)
In-Reply-To: <1465815046-5390-1-git-send-email-julien.grall@arm.com>

On 13/06/16 11:50, Julien Grall wrote:
> The version 1 of the grant-table protocol only supports frame encoded on
> 32-bit.
> 
> When the platform is supporting 48-bit physical address, the frame will
> be encoded on 36-bit which will lead a truncation and give access to
> the wrong frame.
> 
> On ARM Xen will always allow the guest to use all the physical address,
> although today the RAM is always located under 40-bits (see
> xen/include/public/arch-arm.h).
> 
> Add a truncation check in gnttab_update_entry_v1 to prevent the guest to
> give access to the wrong frame.

In hindsight, we shouldn't have dropped the V2 support from Linux.
Should we reinstate it?

David

> Signed-off-by: Julien Grall <julien.grall@arm.com>
> 
> ---
>     This is limiting us to a 44-bit address space whilst ARM can support
>     up to 48-bit today. This number of bit will increase to 52-bit in
>     upcoming processors [1].
> 
>     It might be good to start thinking to extend the version 1 of the
>     protocol to use 64-bit frame number.
> 
>     [1] https://community.arm.com/groups/processors/blog/2016/01/05/armv8-a-architecture-evolution
> ---
>  drivers/xen/grant-table.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/xen/grant-table.c b/drivers/xen/grant-table.c
> index bb36b1e..f47c2e99 100644
> --- a/drivers/xen/grant-table.c
> +++ b/drivers/xen/grant-table.c
> @@ -224,6 +224,13 @@ static void gnttab_update_entry_v1(grant_ref_t ref, domid_t domid,
>  {
>  	gnttab_shared.v1[ref].domid = domid;
>  	gnttab_shared.v1[ref].frame = frame;
> +
> +	/*
> +	 * V1 only supports 32-bit frame, check the truncation
> +	 * to avoid giving access to the wrong frame.
> +	 */
> +	BUG_ON(gnttab_shared.v1[ref].frame != frame);
> +
>  	wmb();
>  	gnttab_shared.v1[ref].flags = flags;
>  }
> 

  reply	other threads:[~2016-06-13 10:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 10:50 [PATCH] xen: grant-table: Check truncation when giving access to a frame Julien Grall
2016-06-13 10:57 ` David Vrabel [this message]
2016-06-13 11:10   ` [Xen-devel] " Julien Grall
2016-06-13 12:20     ` Paul Durrant
2016-06-13 12:12 ` Paul Durrant
2016-06-13 12:41   ` Julien Grall
2016-06-13 12:42     ` Julien Grall
2016-06-13 12:45       ` Paul Durrant
2016-06-13 13:05         ` Julien Grall
2016-06-13 13:14           ` Paul Durrant

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=575E9198.70103@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sstabellini@kernel.org \
    --cc=steve.capper@arm.com \
    --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