[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240325134114.257544-1-david@redhat.com>
Date: Mon, 25 Mar 2024 14:41:11 +0100
From: David Hildenbrand <david@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: linux-mm@...ck.org,
David Hildenbrand <david@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Mike Rapoport <rppt@...nel.org>,
Miklos Szeredi <mszeredi@...hat.com>,
Lorenzo Stoakes <lstoakes@...il.com>,
xingwei lee <xrivendell7@...il.com>,
yue sun <samsun1006219@...il.com>
Subject: [PATCH v1 0/3] mm/secretmem: one fix and one refactoring
Patch #1 fixes a GUP-fast issue, whereby we might succeed in pinning
secretmem folios. Patch #2 extends the memfd_secret selftest to cover
that case. Patch #3 removes folio_is_secretmem() and instead lets
folio_fast_pin_allowed() cover that case as well.
With this series, the reproducer (+selftests) works as expected. To
test patch #3, the gup_longterm test does exactly what we need, and
keeps on working as expected.
Cc: Andrew Morton <akpm@...ux-foundation.org>
Cc: Mike Rapoport (IBM) <rppt@...nel.org>
Cc: Miklos Szeredi <mszeredi@...hat.com>
Cc: Lorenzo Stoakes <lstoakes@...il.com>
Cc: xingwei lee <xrivendell7@...il.com>
Cc: yue sun <samsun1006219@...il.com>
David Hildenbrand (3):
mm/secretmem: fix GUP-fast succeeding on secretmem folios
selftests/memfd_secret: add vmsplice() test
mm: merge folio_is_secretmem() into folio_fast_pin_allowed()
include/linux/secretmem.h | 21 ++---------
mm/gup.c | 33 ++++++++++-------
tools/testing/selftests/mm/memfd_secret.c | 44 +++++++++++++++++++++--
3 files changed, 65 insertions(+), 33 deletions(-)
--
2.43.2
Powered by blists - more mailing lists