From: Li Wang <li.wang@linux.dev>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v3 3/3] mmap24: add test for MAP_32BIT address limit
Date: Sun, 13 Sep 2026 12:18:01 +0800 [thread overview]
Message-ID: <aqYj-Qytv7dq1bl8@linux.dev> (raw)
In-Reply-To: <20260911-mmap_32bit_coverage-v3-3-b0608349556d@suse.com>
> +/*\
> + * Verify that :manpage:`mmap(2)` with the MAP_32BIT flag restricts all mappings
> + * to the first 2GB of the process address space (< 0x80000000).
> + *
> + * MAP_32BIT is supported only on x86-64 for 64-bit programs.
> + *
> + * Use PROT_NONE to test address placement without allocating data pages
> + * or charging private writable memory against the commit limit.
Reviewed-by: Li Wang <li.wang@linux.dev>
This test itself looks good, but unlike the address placement way, maybe we
can create a new test (mmap25.c) that allocates real read-write anonymous memory,
writes a pattern, reads it back, and checks the result.
This verifies that read-write memory mapped with MAP_32BIT functions correctly.
--
Regards,
Li Wang
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-09-13 4:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 15:29 [LTP] [PATCH v3 0/3] mmap testing suite to cover MAP_32BIT Andrea Cervesato
2026-09-11 15:29 ` [LTP] [PATCH v3 1/3] lapi/mmap: add MAP_32BIT fallback Andrea Cervesato
2026-09-11 17:42 ` [LTP] " linuxtestproject.agent
2026-09-13 4:02 ` [LTP] [PATCH v3 1/3] " Li Wang
2026-09-11 15:29 ` [LTP] [PATCH v3 2/3] mmap23: add test for MAP_32BIT oversized mapping Andrea Cervesato
2026-09-13 4:03 ` Li Wang
2026-09-11 15:29 ` [LTP] [PATCH v3 3/3] mmap24: add test for MAP_32BIT address limit Andrea Cervesato
2026-09-13 4:18 ` Li Wang [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=aqYj-Qytv7dq1bl8@linux.dev \
--to=li.wang@linux.dev \
--cc=andrea.cervesato@suse.de \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.