From: Laurent Vivier <laurent@vivier.eu>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2] linux-user/mmap: Return EFAULT/EINVAL for invalid addresses
Date: Tue, 16 Feb 2021 20:13:28 +0100 [thread overview]
Message-ID: <f052a7dd-012e-9011-3fb4-d22f266c6727@vivier.eu> (raw)
In-Reply-To: <6cc082b0f12641ed38675cac776999b184c8020e.camel@linuxfoundation.org>
Le 16/02/2021 à 20:01, Richard Purdie a écrit :
> When using qemu-i386 to build qemux86 webkitgtk on musl, it sits in an
> infinite loop of mremap calls of ever decreasing/increasing addresses.
>
> I suspect something in the musl memory allocation code loops
> indefinitely if it only sees ENOMEM and only exits when it hits other
> errors such as EFAULT or EINVAL.
>
> According to the docs, trying to mremap outside the address space
> can/should return EFAULT and changing this allows the build to succeed.
>
> A better return value for the other cases of invalid addresses is
> EINVAL rather than ENOMEM so adjust the other part of the test to this.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org
>
> Index: qemu-5.2.0/linux-user/mmap.c
> ===================================================================
> --- qemu-5.2.0.orig/linux-user/mmap.c
> +++ qemu-5.2.0/linux-user/mmap.c
> @@ -722,12 +722,14 @@ abi_long target_mremap(abi_ulong old_add
> int prot;
> void *host_addr;
>
> - if (!guest_range_valid(old_addr, old_size) ||
> - ((flags & MREMAP_FIXED) &&
> - !guest_range_valid(new_addr, new_size)) ||
> - ((flags & MREMAP_MAYMOVE) == 0 &&
> - !guest_range_valid(old_addr, new_size))) {
> - errno = ENOMEM;
> + if (!guest_range_valid(old_addr, old_size)) {
> + errno = EFAULT;
> + return -1;
> + }
> +
> + if (((flags & MREMAP_FIXED) && !guest_range_valid(new_addr, new_size)) ||
> + ((flags & MREMAP_MAYMOVE) == 0 && !guest_range_valid(old_addr, new_size))) {
> + errno = EINVAL;
> return -1;
> }
>
>
>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
prev parent reply other threads:[~2021-02-16 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 17:46 [RFC PATCH] linux-user/mmap: Return EFAULT for invalid addresses Richard Purdie
2021-01-22 9:37 ` Richard Purdie
2021-01-22 10:28 ` Philippe Mathieu-Daudé
2021-02-13 17:40 ` Laurent Vivier
2021-02-16 11:49 ` Richard Purdie
2021-02-16 16:21 ` Laurent Vivier
2021-02-16 19:01 ` [PATCH v2] linux-user/mmap: Return EFAULT/EINVAL " Richard Purdie
2021-02-16 19:13 ` 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=f052a7dd-012e-9011-3fb4-d22f266c6727@vivier.eu \
--to=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=richard.purdie@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).