From: Rik van Riel <riel@surriel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Breno Leitao <leitao@debian.org>
Cc: linux-mm@kvack.org, vegard.nossum@oracle.com, rppt@kernel.org,
songmuchun@bytedance.com, shy828301@gmail.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] selftest/mm/hugetlb: SIGBUS on stolen page
Date: Fri, 05 Jan 2024 14:00:58 -0500 [thread overview]
Message-ID: <b074426bb17af70b9db98e7de7023180822a8c40.camel@surriel.com> (raw)
In-Reply-To: <20240105084238.306269c3f3a63cb0fd130baa@linux-foundation.org>
On Fri, 2024-01-05 at 08:42 -0800, Andrew Morton wrote:
> On Fri, 5 Jan 2024 07:54:18 -0800 Breno Leitao <leitao@debian.org>
> wrote:
>
> > This test case triggers a race between madvise(MADV_DONTNEED) and
> > mmap() in a single huge page, which got stolen (while reserved).
> >
> > Once the only page is stolen, the memory previously mmaped (and
> > madvise(MADV_DONTNEED) got a SIGBUS when accessed.
> >
> > I am not adding this test to the un_vmtests.sh scripts, since this
> > test
> > fails at upstream.
>
> Oh. Is a fix for this in the pipeline? If so, I assume that once
> the
> fix is merged, we enable this test in run_vmtests?
>
I've got some ideas on how to fix it, and hope to get
a fix to you and Mike by next week.
I'll ask Mike if I run into any unexpected complications.
--
All Rights Reversed.
prev parent reply other threads:[~2024-01-05 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 15:54 Breno Leitao
2024-01-05 15:54 ` [PATCH 1/1] selftests/mm: new test that steals pages Breno Leitao
2024-01-10 5:47 ` Andrew Morton
2024-01-10 9:18 ` Breno Leitao
2024-01-05 16:42 ` [PATCH 0/1] selftest/mm/hugetlb: SIGBUS on stolen page Andrew Morton
2024-01-05 17:40 ` Breno Leitao
2024-01-05 19:00 ` Rik van Riel [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=b074426bb17af70b9db98e7de7023180822a8c40.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=rppt@kernel.org \
--cc=shy828301@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=vegard.nossum@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox