From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tiejun Chen <tiejun.chen@intel.com>,
JBeulich@suse.com, ian.jackson@eu.citrix.com,
stefano.stabellini@eu.citrix.com, ian.campbell@citrix.com,
yang.z.zhang@intel.com, kevin.tian@intel.com
Cc: xen-devel@lists.xen.org
Subject: Re: [RFC][v3][PATCH 2/6] xen:x86: introduce a new hypercall to get RMRR mappings
Date: Fri, 15 Aug 2014 10:46:31 +0100 [thread overview]
Message-ID: <53EDD6F7.6000500@citrix.com> (raw)
In-Reply-To: <1408091238-18364-3-git-send-email-tiejun.chen@intel.com>
On 15/08/14 09:27, Tiejun Chen wrote:
> We need this new hypercall to get RMRR mapping for VM.
>
> Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
> ---
> xen/arch/x86/x86_64/compat/mm.c | 9 +++++++++
> xen/include/public/memory.h | 14 +++++++++++++-
> 2 files changed, 22 insertions(+), 1 deletion(-)
>
> diff --git a/xen/arch/x86/x86_64/compat/mm.c b/xen/arch/x86/x86_64/compat/mm.c
> index 69c6195..ff16f17 100644
> --- a/xen/arch/x86/x86_64/compat/mm.c
> +++ b/xen/arch/x86/x86_64/compat/mm.c
> @@ -132,6 +132,15 @@ int compat_arch_memory_op(unsigned long cmd, XEN_GUEST_HANDLE_PARAM(void) arg)
> break;
> }
>
> + case XENMEM_reserved_device_memory_map:
> + {
> + /* Currently we just need to cover RMRR. */
> + if ( copy_to_guest(arg, &rmrr_maps, 1) )
> + return -EFAULT;
This will trivially clobber the hypercaller's stack/heap.
You are not even using the correct indirection of
xen_rmrr_memory_map_t.buffer
You *must* start by copying xen_rmrr_memory_map_t from the guest.
~Andrew
> +
> + return 0;
> + }
> +
> case XENMEM_machphys_mapping:
> {
> struct domain *d = current->domain;
> diff --git a/xen/include/public/memory.h b/xen/include/public/memory.h
> index 2c57aa0..13e539f 100644
> --- a/xen/include/public/memory.h
> +++ b/xen/include/public/memory.h
> @@ -523,7 +523,19 @@ DEFINE_XEN_GUEST_HANDLE(xen_mem_sharing_op_t);
>
> #endif /* defined(__XEN__) || defined(__XEN_TOOLS__) */
>
> -/* Next available subop number is 26 */
> +/*
> + * Some devices may reserve some range.
> + *
> + * Currently we just have RMRR
> + * - Reserved memory Region Reporting Structure,
> + * So returns the RMRR memory map as it was when the domain
> + * was started.
> + */
> +#define XENMEM_reserved_device_memory_map 26
> +typedef struct xen_memory_map xen_rmrr_memory_map_t;
> +DEFINE_XEN_GUEST_HANDLE(xen_rmrr_memory_map_t);
> +
> +/* Next available subop number is 27 */
>
> #endif /* __XEN_PUBLIC_MEMORY_H__ */
>
next prev parent reply other threads:[~2014-08-15 9:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 8:27 [RFC][v3][PATCH 0/6] xen: reserve RMRR to avoid conflicting MMIO/RAM Tiejun Chen
2014-08-15 8:27 ` [RFC][v3][PATCH 1/6] xen:x86: record RMRR mappings Tiejun Chen
2014-08-15 9:39 ` Andrew Cooper
2014-08-15 16:29 ` Jan Beulich
2014-08-18 7:42 ` Chen, Tiejun
2014-08-18 9:57 ` Andrew Cooper
2014-08-18 10:05 ` Chen, Tiejun
2014-08-18 12:31 ` Jan Beulich
2014-08-19 2:14 ` Chen, Tiejun
2014-08-19 2:28 ` Chen, Tiejun
2014-08-19 13:12 ` Jan Beulich
2014-08-18 7:45 ` Chen, Tiejun
2014-08-18 9:51 ` Andrew Cooper
2014-08-18 10:01 ` Chen, Tiejun
2014-08-18 12:56 ` Jan Beulich
2014-08-15 8:27 ` [RFC][v3][PATCH 2/6] xen:x86: introduce a new hypercall to get " Tiejun Chen
2014-08-15 9:46 ` Andrew Cooper [this message]
2014-08-18 7:46 ` Chen, Tiejun
2014-08-15 8:27 ` [RFC][v3][PATCH 3/6] tools:firmware:hvmloader: reserve RMRR mappings in e820 Tiejun Chen
2014-08-15 9:58 ` Andrew Cooper
2014-08-18 7:51 ` Chen, Tiejun
2014-08-18 10:00 ` Andrew Cooper
2014-08-15 8:27 ` [RFC][v3][PATCH 4/6] xen:x86: add XENMEM_reserved_device_memory_map to expose RMRR Tiejun Chen
2014-08-15 12:15 ` Andrew Cooper
2014-08-18 8:00 ` Chen, Tiejun
2014-08-18 10:06 ` Andrew Cooper
2014-08-15 8:27 ` [RFC][v3][PATCH 5/6] tools:libxc: check if mmio BAR is out of RMRR mappings Tiejun Chen
2014-08-15 12:21 ` Andrew Cooper
2014-08-18 8:05 ` Chen, Tiejun
2014-08-15 8:27 ` [RFC][v3][PATCH 6/6] xen:vtd: make USB RMRR mapping safe Tiejun Chen
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=53EDD6F7.6000500@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tiejun.chen@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.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).