qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "Kyle Evans" <kevans@freebsd.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH v2 8/9] bsd-user/mmap.c: Implement MAP_EXCL, required by jemalloc in head
Date: Sun, 26 Sep 2021 12:38:08 -0600	[thread overview]
Message-ID: <CANCZdfoYpA0ShW6G1+9WixbGsPFZLSN13i9qxgc6J3qu3t=aaw@mail.gmail.com> (raw)
In-Reply-To: <4d7f5ce6-22c4-e9de-39c6-fb92d7096385@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

On Fri, Sep 24, 2021 at 6:00 AM Richard Henderson <
richard.henderson@linaro.org> wrote:

> On 9/21/21 9:56 PM, Warner Losh wrote:
> > +        /* Reject the mapping if any page within the range is mapped */
> > +        if (flags & MAP_EXCL) {
> > +            for (addr = start; addr < end; addr++) {
> > +                if (page_get_flags(addr) != 0)
> > +                    goto fail;
> > +            }
> > +        }
>
> How about
>
>      if ((flags & MAP_EXCL) &&
>          page_check_range(start, len, 0) < 0) {
>         goto fail;
>      }
>
> Hmm.  This (and your page_get_flags check) could assert due to
> out-of-range guest address.
>   You're currently attempting that,
>
>          /*
>           * Test if requested memory area fits target address space
>           * It can fail only on 64-bit host with 32-bit target.
>           * On any other target/host host mmap() handles this error
> correctly.
>           */
> #if TARGET_ABI_BITS == 32 && HOST_LONG_BITS == 64
>          if ((unsigned long)start + len - 1 > (abi_ulong) -1) {
>              errno = EINVAL;
>              goto fail;
>          }
> #endif
>
> but the test isn't correct.  Note that reserved_va may be applied to
> 64-bit guests, and
> certainly may be smaller than (abi_ulong)-1.
>
> You want guest_range_valid_untagged here.
>

Great! Thanks for the tip!

Warner

[-- Attachment #2: Type: text/html, Size: 1999 bytes --]

  reply	other threads:[~2021-09-26 18:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22  4:56 [PATCH v2 0/9] bsd-user mmap fixes Warner Losh
2021-09-22  4:56 ` [PATCH v2 1/9] bsd-user/mmap.c: Always zero MAP_ANONYMOUS memory in mmap_frag() Warner Losh
2021-09-23 17:35   ` Richard Henderson
2021-09-22  4:56 ` [PATCH v2 2/9] bsd-user/mmap.c: check pread's return value to fix warnings with _FORTIFY_SOURCE Warner Losh
2021-09-23 17:36   ` Richard Henderson
2021-09-24 15:07     ` Warner Losh
2021-09-25 10:54   ` Philippe Mathieu-Daudé
2021-09-22  4:56 ` [PATCH v2 3/9] bsd-user/mmap.c: MAP_ symbols are defined, so no need for ifdefs Warner Losh
2021-09-23 17:37   ` Richard Henderson
2021-09-22  4:56 ` [PATCH v2 4/9] bsd-user/mmap.c: mmap return ENOMEM on overflow Warner Losh
2021-09-23 17:38   ` Richard Henderson
2021-09-25 10:55   ` Philippe Mathieu-Daudé
2021-09-22  4:56 ` [PATCH v2 5/9] bsd-user/mmap.c: mmap prefer MAP_ANON for BSD Warner Losh
2021-09-23 17:38   ` Richard Henderson
2021-09-22  4:56 ` [PATCH v2 6/9] bsd-user/mmap.c: line wrap change Warner Losh
2021-09-23 17:41   ` Richard Henderson
2021-09-26 16:46     ` Warner Losh
2021-09-22  4:56 ` [PATCH v2 7/9] bsd-user/mmap.c: Don't mmap fd == -1 independently from MAP_ANON flag Warner Losh
2021-09-23 17:43   ` Richard Henderson
2021-09-26 17:08     ` Warner Losh
2021-09-26 19:07       ` Guy Yur
2021-09-27  0:17         ` Warner Losh
2021-09-22  4:56 ` [PATCH v2 8/9] bsd-user/mmap.c: Implement MAP_EXCL, required by jemalloc in head Warner Losh
2021-09-23 17:52   ` Richard Henderson
2021-09-26 18:38     ` Warner Losh [this message]
2021-09-22  4:56 ` [PATCH v2 9/9] bsd-user/mmap.c: assert that target_mprotect cannot fail Warner Losh
2021-09-23 17:53   ` Richard Henderson
2021-09-25 10:58   ` Philippe Mathieu-Daudé

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='CANCZdfoYpA0ShW6G1+9WixbGsPFZLSN13i9qxgc6J3qu3t=aaw@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=f4bug@amsat.org \
    --cc=kevans@freebsd.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).