From: Gregory Price <gourry@gourry.net>
To: Zenghui Yu <zenghui.yu@linux.dev>
Cc: linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
david@kernel.org, ljs@kernel.org, liam@infradead.org,
vbabka@kernel.org, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, shuah@kernel.org
Subject: Re: [PATCH] selftests/mm: fix size truncation in pagemap_ioctl test
Date: Mon, 7 Sep 2026 10:57:42 -0400 [thread overview]
Message-ID: <ap7Qza32A-MzxBU3@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20260907135613.68692-1-zenghui.yu@linux.dev>
On Mon, Sep 07, 2026 at 09:56:13PM +0800, Zenghui Yu wrote:
> From: "Zenghui Yu (Huawei)" <zenghui.yu@linux.dev>
>
> On arm64 with 64K base pages, the huge page size is 512 MiB, and
> hpage_unit_tests() builds a 5 GiB range (10 * 512 MiB) for its tests. This
> exceeds the range of the int size parameters of gethugepage(),
> wp_addr_range() and pagemap_ioctl(). The implicit truncation to 1 GiB
> makes gethugepage() allocate a too small buffer, while the callers keep
> operating on the original 5 GiB range, resulting in spurious failures or
> SIGSEGV.
>
> Change those size parameters to size_t.
>
> Fixes: 46fd75d4a3c9 ("selftests: mm: add pagemap ioctl tests")
> Assisted-by: GLM-5.3 OpenCode
> Signed-off-by: Zenghui Yu (Huawei) <zenghui.yu@linux.dev>
Reviewed-by: Gregory Price (Meta) <gourry@gourry.net>
> ---
> tools/testing/selftests/mm/pagemap_ioctl.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/testing/selftests/mm/pagemap_ioctl.c b/tools/testing/selftests/mm/pagemap_ioctl.c
> index eadc7159ca5b..48cbea3a33c9 100644
> --- a/tools/testing/selftests/mm/pagemap_ioctl.c
> +++ b/tools/testing/selftests/mm/pagemap_ioctl.c
> @@ -44,7 +44,7 @@ const char *progname;
>
> #define LEN(region) ((region.end - region.start)/page_size)
>
> -static long pagemap_ioctl(void *start, int len, void *vec, int vec_len, int flag,
> +static long pagemap_ioctl(void *start, size_t len, void *vec, int vec_len, int flag,
> int max_pages, long required_mask, long anyof_mask, long excluded_mask,
> long return_mask)
> {
> @@ -152,7 +152,7 @@ int wp_free(void *addr, long size)
> return 0;
> }
>
> -int wp_addr_range(void *addr, int size)
> +int wp_addr_range(void *addr, size_t size)
> {
> if (pagemap_ioctl(addr, size, NULL, 0,
> PM_SCAN_WP_MATCHING | PM_SCAN_CHECK_WPASYNC,
> @@ -787,7 +787,7 @@ int base_tests(char *prefix, char *mem, unsigned long long mem_size, int skip)
> return 0;
> }
>
> -void *gethugepage(int map_size)
> +void *gethugepage(size_t map_size)
> {
> int ret;
> char *map;
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-09-07 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 13:56 Zenghui Yu
2026-09-07 14:57 ` Gregory Price [this message]
2026-09-07 15:22 ` David Hildenbrand (Arm)
2026-09-08 11:22 ` Zenghui Yu
2026-09-08 12:38 ` David Hildenbrand (Arm)
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=ap7Qza32A-MzxBU3@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=zenghui.yu@linux.dev \
/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
all inboxes | Powered by JetHome®