mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Nico Pache <npache@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-mm@kvack.org, shuah@kernel.org,
	donettom@linux.vnet.ibm.com,
	Christophe Leroy <christophe.leroy@c-s.fr>,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH v2] selftests: mm: fix map_hugetlb failure on 64K page size systems
Date: Sat, 20 Jan 2024 20:39:04 -0800	[thread overview]
Message-ID: <20240120203904.8f36140cd2f507b25e9a09a3@linux-foundation.org> (raw)
In-Reply-To: <20240119131429.172448-1-npache@redhat.com>

On Fri, 19 Jan 2024 06:14:29 -0700 Nico Pache <npache@redhat.com> wrote:

> On systems with 64k page size and 512M huge page sizes, the allocation
> and test succeeds but errors out at the munmap. As the comment states,
> munmap will failure if its not HUGEPAGE aligned. This is due to the
> length of the mapping being 1/2 the size of the hugepage causing the
> munmap to not be hugepage aligned. Fix this by making the mapping length
> the full hugepage if the hugepage is larger than the length of the
> mapping.

Is

Fixes: fa7b9a805c79 ("tools/selftest/vm: allow choosing mem size and page size in map_hugetlb")

a suitable Fixes: target for this?

> --- a/tools/testing/selftests/mm/map_hugetlb.c
> +++ b/tools/testing/selftests/mm/map_hugetlb.c
> @@ -15,6 +15,7 @@
>  #include <unistd.h>
>  #include <sys/mman.h>
>  #include <fcntl.h>
> +#include "vm_util.h"
>  
>  #define LENGTH (256UL*1024*1024)
>  #define PROTECTION (PROT_READ | PROT_WRITE)
> @@ -58,10 +59,16 @@ int main(int argc, char **argv)
>  {
>  	void *addr;
>  	int ret;
> +	size_t hugepage_size;
>  	size_t length = LENGTH;
>  	int flags = FLAGS;
>  	int shift = 0;
>  
> +	hugepage_size = default_huge_page_size();
> +	/* munmap with fail if the length is not page aligned */
> +	if (hugepage_size > length)
> +		length = hugepage_size;
> +
>  	if (argc > 1)
>  		length = atol(argv[1]) << 20;
>  	if (argc > 2) {
> -- 
> 2.43.0

  reply	other threads:[~2024-01-21  4:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 13:14 Nico Pache
2024-01-21  4:39 ` Andrew Morton [this message]
2024-01-22 14:08   ` Nico Pache

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=20240120203904.8f36140cd2f507b25e9a09a3@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=christophe.leroy@c-s.fr \
    --cc=donettom@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mpe@ellerman.id.au \
    --cc=npache@redhat.com \
    --cc=shuah@kernel.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

all inboxes | Powered by JetHome®