From: Laurent Vivier <laurent@vivier.eu>
To: Max Filippov <jcmvbkbc@gmail.com>, qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v6 05/11] linux-user: fix mmap/munmap/mprotect/mremap/shmat
Date: Fri, 9 Mar 2018 20:55:25 +0100 [thread overview]
Message-ID: <22d1a396-c59c-b546-6d0b-52302a7b69db@vivier.eu> (raw)
In-Reply-To: <20180307215010.30706-1-jcmvbkbc@gmail.com>
Le 07/03/2018 à 22:50, 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.
>
> Change definition of GUEST_ADDR_MAX to always be the last valid guest
> address. Account for this change in open_self_maps.
> Add macro guest_addr_valid that verifies if the guest address is valid.
> Add function 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 v5->v6:
> - drop 'if (len)' clause from guest_range_valid and explicitly compare
> len with GUEST_ADDR_MAX.
>
> Changes v4->v5:
> - change definition of GUEST_ADDR_MAX to always be the last valid guest
> address. Account for this change in guest_addr_valid and open_self_maps.
> - turn guest_range_valid into a function.
>
> Changes v3->v4:
> - change GUEST_ADDR_MAX and h2g_valid definitions as suggested by Laurent
> Vivier.
>
> 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.
>
> include/exec/cpu-all.h | 6 +++++-
> include/exec/cpu_ldst.h | 16 +++++++---------
> linux-user/mmap.c | 20 +++++++++++++++-----
> linux-user/syscall.c | 5 ++++-
> 4 files changed, 31 insertions(+), 16 deletions(-)
>
Applied to my 'linux-user-for-2.12' branch.
Thanks,
Laurent
prev parent reply other threads:[~2018-03-09 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 21:50 [Qemu-devel] [PATCH v6 05/11] linux-user: fix mmap/munmap/mprotect/mremap/shmat Max Filippov
2018-03-08 7:19 ` Laurent Vivier
2018-03-09 19:55 ` Laurent Vivier [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=22d1a396-c59c-b546-6d0b-52302a7b69db@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).