qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Max Filippov <jcmvbkbc@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PATCH v3 05/11] linux-user: fix mmap/munmap/mprotect/mremap/shmat
Date: Tue, 6 Mar 2018 13:02:59 +0100	[thread overview]
Message-ID: <91b370e2-d5aa-98b9-a005-2fe8f77881ee@vivier.eu> (raw)
In-Reply-To: <20180301173636.19082-1-jcmvbkbc@gmail.com>

Le 01/03/2018 à 18:36, Max Filippov a écrit :
> In linux-user QEMU that runs for a target with TARGET_ABI_BITS bigger
> than L1_MAP_ADDR_SPACE_BITS an assertion in page_set_flags fires when
> mmap, munmap, mprotect, mremap or shmat is called for an address outside
> the guest address space. mmap and mprotect should return ENOMEM in such
> case.
> 
> Introduce macro guest_range_valid that verifies if address range is
> within guest address space and does not wrap around. Use that macro in
> mmap/munmap/mprotect/mremap/shmat for error checking.
> 
> Cc: qemu-stable@nongnu.org
> Cc: Riku Voipio <riku.voipio@iki.fi>
> Cc: Laurent Vivier <laurent@vivier.eu>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
> Changes v2->v3:
> - fix comparison in guest_valid: it must be 'less' to preserve the existing
>   functionality, not 'less or equal'.
> - fix guest_range_valid: it may not use guest_valid, because single range
>   that occupies all of the guest address space is valid.
> 
> These changes fix assertion in page_check_range called from open_self_maps.
> 
>  include/exec/cpu-all.h  |  2 +-
>  include/exec/cpu_ldst.h | 12 +++++++-----
>  linux-user/mmap.c       | 20 +++++++++++++++-----
>  linux-user/syscall.c    |  3 +++
>  4 files changed, 26 insertions(+), 11 deletions(-)
> 
> diff --git a/include/exec/cpu-all.h b/include/exec/cpu-all.h
> index 0b141683f095..12bd049997ac 100644
> --- a/include/exec/cpu-all.h
> +++ b/include/exec/cpu-all.h
> @@ -160,7 +160,7 @@ extern int have_guest_base;
>  extern unsigned long reserved_va;
>  
>  #define GUEST_ADDR_MAX (reserved_va ? reserved_va : \
> -                                    (1ul << TARGET_VIRT_ADDR_SPACE_BITS) - 1)
> +                        (2ul << (TARGET_VIRT_ADDR_SPACE_BITS - 1)) - 1)

I don't understand why you do this change. Could you explain?

>  #else
>  
>  #include "exec/hwaddr.h"
> diff --git a/include/exec/cpu_ldst.h b/include/exec/cpu_ldst.h
> index 191f2e962a3c..6528fd829ffe 100644
> --- a/include/exec/cpu_ldst.h
> +++ b/include/exec/cpu_ldst.h
> @@ -53,14 +53,16 @@
>  
>  #if HOST_LONG_BITS <= TARGET_VIRT_ADDR_SPACE_BITS
>  #define h2g_valid(x) 1
> +#define guest_valid(x) 1
>  #else
> -#define h2g_valid(x) ({ \
> -    unsigned long __guest = (unsigned long)(x) - guest_base; \
> -    (__guest < (1ul << TARGET_VIRT_ADDR_SPACE_BITS)) && \
> -    (!reserved_va || (__guest < reserved_va)); \
> -})
> +#define h2g_valid(x) guest_valid((unsigned long)(x) - guest_base)
> +#define guest_valid(x) ((x) < GUEST_ADDR_MAX)
>  #endif

I think you can just define h2g_valid(x) after the "endif":

  #define h2g_valid(x) guest_valid((unsigned long)(x) - guest_base)

it will be set according to the guest_valid() definition ("1" or the
result of the evaluation).

Thanks,
Laurent

  reply	other threads:[~2018-03-06 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 17:36 [Qemu-devel] [PATCH v3 05/11] linux-user: fix mmap/munmap/mprotect/mremap/shmat Max Filippov
2018-03-06 12:02 ` Laurent Vivier [this message]
2018-03-06 17:28   ` Max Filippov
2018-03-06 17:39     ` Laurent Vivier
2018-03-06 17:50       ` Max Filippov

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=91b370e2-d5aa-98b9-a005-2fe8f77881ee@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=jcmvbkbc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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).