From: Richard Cheng <icheng@nvidia.com>
To: akpm@linux-foundation.org, david@kernel.org
Cc: jgg@ziepe.ca, jhubbard@nvidia.com, peterx@redhat.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org, ljs@kernel.org,
liam@infradead.org, vbabka@kernel.org, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, kobak@nvidia.com,
kaihengf@nvidia.com, newtonl@nvidia.com, kristinc@nvidia.com,
Richard Cheng <icheng@nvidia.com>
Subject: [RFC PATCH 0/2] Fix gup_test long-term pin ownership
Date: Mon, 21 Sep 2026 17:42:41 +0800 [thread overview]
Message-ID: <20260921094243.64698-1-icheng@nvidia.com> (raw)
gup_test currently stores long-term pin state globally, allowing one
open file descriptor to block or release pins owned by another client.
Move this state to each open file description so independent clients
have isolated pin lifecycles.
Patch 1 moves long-term pin state from global variables to per-open
file state, preventing independent clients from affecting each other.
Patch 2 adds selftest coverage for concurrent pins and verifies that
stopping or closing one descriptor does not release another
descriptor's pin.
Richard Cheng (2):
mm/gup_test: Track long-term pins per open file
selftests/mm: Test per-open gup_test pin ownership
mm/gup_test.c | 88 +++++---
tools/testing/selftests/mm/gup_longterm.c | 258 +++++++++++++++++++++-
2 files changed, 313 insertions(+), 33 deletions(-)
base-commit: 66498c75b4f8017f62d720d9b59675bdf3abce91
--
2.43.0
next reply other threads:[~2026-09-21 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 9:42 Richard Cheng [this message]
2026-09-21 9:42 ` [RFC PATCH 1/2] mm/gup_test: Track long-term pins per open file Richard Cheng
2026-09-21 10:26 ` David Hildenbrand (Arm)
2026-09-21 9:42 ` [RFC PATCH 2/2] selftests/mm: Test per-open gup_test pin ownership Richard Cheng
2026-09-21 10:28 ` David Hildenbrand (Arm)
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=20260921094243.64698-1-icheng@nvidia.com \
--to=icheng@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kaihengf@nvidia.com \
--cc=kobak@nvidia.com \
--cc=kristinc@nvidia.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=newtonl@nvidia.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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®