All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: Tarun Sahu <tsahu@linux.ibm.com>
Cc: sbhat@linux.ibm.com, aneesh.kumar@linux.ibm.com,
	geetika@linux.ibm.com, vaibhav@linux.ibm.com,
	rpalethorpe@suse.com, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 06/13] Hugetlb: Migrating libhugetlbfs mremap-fixed-normal-near-huge
Date: Tue, 27 Dec 2022 14:31:07 +0800	[thread overview]
Message-ID: <CAEemH2fOB=NSnCt=JMhpDU49MwHvP+z7hjmUoEXi-BEM-tvqCw@mail.gmail.com> (raw)
In-Reply-To: <20221225154213.84183-7-tsahu@linux.ibm.com>

On Sun, Dec 25, 2022 at 11:42 PM Tarun Sahu <tsahu@linux.ibm.com> wrote:

> Migrating the libhugetlbfs/testcases/mremap-fixed-normal-near-huge.c test
>
> Test Description: The kernel has bug for mremap() on some architecture.
> mremap() can cause crashes on architectures with holes in the address
> space (like ia64) and on powerpc with it's distinct page size "slices".
>
> This test get the huge mapping address and mremap() normal mapping
> near to this huge mapping.
>
> Signed-off-by: Tarun Sahu <tsahu@linux.ibm.com>
> ---
>  runtest/hugetlb                               |   1 +
>  testcases/kernel/mem/.gitignore               |   1 +
>  .../kernel/mem/hugetlb/hugemmap/hugemmap26.c  | 131 ++++++++++++++++++
>  3 files changed, 133 insertions(+)
>  create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap26.c
>
> diff --git a/runtest/hugetlb b/runtest/hugetlb
> index 65265b0fe..55185f2f7 100644
> --- a/runtest/hugetlb
> +++ b/runtest/hugetlb
> @@ -26,6 +26,7 @@ hugemmap21 hugemmap21
>  hugemmap22 hugemmap22
>  hugemmap23 hugemmap23
>  hugemmap25 hugemmap25
> +hugemmap26 hugemmap26
>  hugemmap05_1 hugemmap05 -m
>  hugemmap05_2 hugemmap05 -s
>  hugemmap05_3 hugemmap05 -s -m
> diff --git a/testcases/kernel/mem/.gitignore
> b/testcases/kernel/mem/.gitignore
> index c865a1e55..4886c6a5f 100644
> --- a/testcases/kernel/mem/.gitignore
> +++ b/testcases/kernel/mem/.gitignore
> @@ -25,6 +25,7 @@
>  /hugetlb/hugemmap/hugemmap22
>  /hugetlb/hugemmap/hugemmap23
>  /hugetlb/hugemmap/hugemmap25
> +/hugetlb/hugemmap/hugemmap26
>  /hugetlb/hugeshmat/hugeshmat01
>  /hugetlb/hugeshmat/hugeshmat02
>  /hugetlb/hugeshmat/hugeshmat03
> diff --git a/testcases/kernel/mem/hugetlb/hugemmap/hugemmap26.c
> b/testcases/kernel/mem/hugetlb/hugemmap/hugemmap26.c
> new file mode 100644
> index 000000000..03dd248bd
> --- /dev/null
> +++ b/testcases/kernel/mem/hugetlb/hugemmap/hugemmap26.c
> @@ -0,0 +1,131 @@
> +// SPDX-License-Identifier: LGPL-2.1-or-later
> +/*
> + * Copyright (C) 2009 IBM Corporation.
> + * Author: David Gibson
> + */
> +
> +/*\
> + * [Description]
> + *
> + * Test Description: The kernel has bug for mremap() on some architecture.
> + * mremap() can cause crashes on architectures with holes in the address
> + * space (like ia64) and on powerpc with it's distinct page size "slices".
> + *
> + * This test get the huge mapping address and mremap() normal mapping
> + * near to this huge mapping.
> + */
> +
> +#define _GNU_SOURCE
> +#include <stdio.h>
> +#include <sys/mount.h>
> +#include <limits.h>
> +#include <sys/param.h>
> +#include <sys/types.h>
> +
> +#include "hugetlb.h"
> +
> +#define RANDOM_CONSTANT        0x1234ABCD
> +#define MNTPOINT "hugetlbfs/"
> +
> +static int  fd = -1;
> +static long hpage_size, page_size;
> +
> +static int do_readback(void *p, size_t size, const char *stage)
> +{
> +       unsigned int *q = p;
> +       size_t i;
> +
> +       tst_res(TINFO, "%s(%p, 0x%lx, \"%s\")", __func__, p,
> +              (unsigned long)size, stage);
> +
> +       for (i = 0; i < (size / sizeof(*q)); i++)
> +               q[i] = RANDOM_CONSTANT ^ i;
> +
> +       for (i = 0; i < (size / sizeof(*q)); i++) {
> +               if (q[i] != (RANDOM_CONSTANT ^ i)) {
> +                       tst_res(TFAIL, "Stage \"%s\": Mismatch at offset
> 0x%lx: 0x%x "
> +                                       "instead of 0x%lx", stage, i,
> q[i], RANDOM_CONSTANT ^ i);
> +                       return -1;
> +               }
> +       }
> +       return 0;
> +}
> +
> +static int do_remap(void *target)
> +{
> +       void *a, *b;
> +       int ret;
> +
> +       a = SAFE_MMAP(NULL, page_size, PROT_READ|PROT_WRITE,
> +                 MAP_SHARED|MAP_ANONYMOUS, -1, 0);
> +
> +       ret = do_readback(a, page_size, "base normal");
> +       if (ret)
> +               goto cleanup;
> +       b = mremap(a, page_size, page_size, MREMAP_MAYMOVE | MREMAP_FIXED,
> +                  target);
> +
> +       if (b != MAP_FAILED) {
> +               do_readback(b, page_size, "remapped");
> +               a = b;
> +       } else
> +               tst_res(TINFO|TERRNO, "mremap(MAYMOVE|FIXED) disallowed");
> +
> +cleanup:
> +       SAFE_MUNMAP(a, page_size);
> +       return ret;
> +}
>

Those two functions do_readback() and do_remap() are
copy&past from hugemmap2[4|5].c, what about extracting
them into a common header file(tst_hugetlb.h or mem.h) for
easy reusing?

And I also noticed other tests (hugemmap27) using the same
macro mem barrier(), it'd be great to define it in a header file.


-- 
Regards,
Li Wang

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-12-27  6:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-25 15:42 [LTP] [PATCH 0/13][PART 4] Hugetlb:Migrating the libhugetlbfs tests Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 01/13] Hugetlb: Migrating libhugetlbfs mlock Tarun Sahu
2022-12-26  4:48   ` Li Wang
2022-12-26  9:39     ` Tarun Sahu
2022-12-26  9:48       ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 02/13] Hugetlb: Migrating libhugetlbfs mmap-cow Tarun Sahu
2022-12-26  6:57   ` Li Wang
2022-12-26  7:35     ` Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 03/13] Hugetlb: Migrating libhugetlbfs mmap-gettest Tarun Sahu
2022-12-26  7:33   ` Li Wang
2022-12-26  9:41     ` Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 04/13] Hugetlb: Migrating libhugetlbfs mprotect Tarun Sahu
2022-12-27  5:48   ` Li Wang
2022-12-27 16:00     ` Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 05/13] Hugetlb: Migrating libhugetlbfs mremap-fixed-huge-near-normal Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 06/13] Hugetlb: Migrating libhugetlbfs mremap-fixed-normal-near-huge Tarun Sahu
2022-12-27  6:31   ` Li Wang [this message]
2022-12-27 18:21     ` Tarun Sahu
2022-12-29 19:06       ` Tarun Sahu
2022-12-30  3:49         ` Li Wang
2022-12-31  5:08           ` Tarun Sahu
2023-01-03  3:06             ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 07/13] Hugetlb: Migrating libhugetlbfs noresv-reserve-resv-page Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 08/13] Hugetlb: Migrating libhugetlbfs noresv-regarded-as-resv Tarun Sahu
2022-12-27  6:47   ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 09/13] Hugetlb: Migrating libhugetlbfs private Tarun Sahu
2022-12-27  6:56   ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 10/13] Hugetlb: Migrating libhugetlbfs readahead_reserve Tarun Sahu
2022-12-27  7:05   ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 11/13] Hugetlb: Migrating libhugetlbfs shared Tarun Sahu
2022-12-27  7:08   ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 12/13] Hugetlb: Migrating libhugetlbfs shm-fork Tarun Sahu
2022-12-28  3:15   ` Li Wang
2023-01-03 18:23   ` Petr Vorel
2023-01-04 17:59     ` Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 13/13] Hugetlb: Migrating libhugetlbfs mremap-expand-slice-collision Tarun Sahu

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='CAEemH2fOB=NSnCt=JMhpDU49MwHvP+z7hjmUoEXi-BEM-tvqCw@mail.gmail.com' \
    --to=liwang@redhat.com \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=geetika@linux.ibm.com \
    --cc=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.com \
    --cc=sbhat@linux.ibm.com \
    --cc=tsahu@linux.ibm.com \
    --cc=vaibhav@linux.ibm.com \
    /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.