From: Alistair Popple <apopple@nvidia.com>
To: linux-mm@kvack.org
Cc: zenghui.yu@linux.dev, Liam.Howlett@oracle.com,
akpm@linux-foundation.org, david@kernel.org, jgg@ziepe.ca,
leon@kernel.org, linux-kernel@vger.kernel.org, ljs@kernel.org,
mhocko@suse.com, rppt@kernel.org, surenb@google.com,
vbabka@kernel.org, dri-devel@lists.freedesktop.org,
balbirs@nvidia.com, Alistair Popple <apopple@nvidia.com>
Subject: [PATCH 0/3] Minor hmm_test fixes and cleanups
Date: Tue, 31 Mar 2026 17:34:42 +1100 [thread overview]
Message-ID: <20260331063445.3551404-1-apopple@nvidia.com> (raw)
Just a couple of minor fixups and cleanups for the HMM kernel selftests. These
were mostly reported by Zenghui Yu with special thanks to Lorenzo for analysing
and pointing out the problems.
Alistair Popple (3):
lib: test_hmm: evict device pages on file close to avoid
use-after-free
selftests/mm: hmm-tests: don't hardcode THP size to 2MB
lib: test_hmm: Implement a device release method
lib/test_hmm.c | 130 +++++++++++++++----------
tools/testing/selftests/mm/hmm-tests.c | 83 +++-------------
2 files changed, 93 insertions(+), 120 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-31 6:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 6:34 Alistair Popple [this message]
2026-03-31 6:34 ` [PATCH 1/3] lib: test_hmm: evict device pages on file close to avoid use-after-free Alistair Popple
2026-03-31 8:47 ` Balbir Singh
2026-04-05 4:35 ` Zenghui Yu
2026-04-05 4:47 ` Zenghui Yu
2026-03-31 6:34 ` [PATCH 2/3] selftests/mm: hmm-tests: don't hardcode THP size to 2MB Alistair Popple
2026-03-31 8:51 ` Balbir Singh
2026-04-01 5:19 ` Matthew Brost
2026-04-01 23:01 ` Matthew Brost
2026-04-02 6:32 ` Sayali Patil
2026-03-31 6:34 ` [PATCH 3/3] lib: test_hmm: Implement a device release method Alistair Popple
2026-03-31 8:53 ` Balbir Singh
2026-04-05 4:47 ` Zenghui Yu
2026-04-01 0:33 ` [PATCH 0/3] Minor hmm_test fixes and cleanups Andrew Morton
2026-04-01 1:20 ` Alistair Popple
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=20260331063445.3551404-1-apopple@nvidia.com \
--to=apopple@nvidia.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=balbirs@nvidia.com \
--cc=david@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@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