From: Rik van Riel <riel@surriel.com>
To: Breno Leitao <leitao@debian.org>,
mike.kravetz@oracle.com, muchun.song@linux.dev,
akpm@linux-foundation.org, Shuah Khan <shuah@kernel.org>
Cc: linux-mm@kvack.org, open list <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] selftests/mm: Add a new test for madv and hugetlb
Date: Thu, 05 Oct 2023 23:55:47 -0400 [thread overview]
Message-ID: <6ab947df00886d80bd476121cd2c703eda91f318.camel@surriel.com> (raw)
In-Reply-To: <20231005163922.87568-3-leitao@debian.org>
On Thu, 2023-10-05 at 09:39 -0700, Breno Leitao wrote:
> Create a selftest that exercises the race between page faults and
> madvise(MADV_DONTNEED) in the same huge page. Do it by running two
> threads that touches the huge page and madvise(MADV_DONTNEED) at the
> same
> time.
>
> ----------------------------------
> ./run_vmtests.sh: line 186: 595563 Bus error (core dumped) "$@"
> [FAIL]
>
> This selftest goes together with the fix of the bug[1] itself.
>
> [1]
> https://lore.kernel.org/all/20231001005659.2185316-1-riel@surriel.com/#r
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
Tested-and-reviewed-by: Rik van Riel <riel@surriel.com>
--
All Rights Reversed.
next prev parent reply other threads:[~2023-10-06 3:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 16:39 [PATCH v2 0/2] New selftest for mm Breno Leitao
2023-10-05 16:39 ` [PATCH v2 1/2] selftests/mm: export get_free_hugepages() Breno Leitao
2023-10-06 3:54 ` Rik van Riel
2023-10-05 16:39 ` [PATCH v2 2/2] selftests/mm: Add a new test for madv and hugetlb Breno Leitao
2023-10-06 3:55 ` Rik van Riel [this message]
2023-11-02 12:24 ` Ryan Roberts
2023-11-02 12:29 ` Ryan Roberts
2023-11-03 13:59 ` Breno Leitao
2023-11-03 14:47 ` Ryan Roberts
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=6ab947df00886d80bd476121cd2c703eda91f318.camel@surriel.com \
--to=riel@surriel.com \
--cc=akpm@linux-foundation.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--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