From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Anthony Yznaga <anthony.yznaga@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Cc: akpm@linux-foundation.org, ljs@kernel.org,
Liam.Howlett@oracle.com, vbabka@kernel.org, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, jannh@google.com,
pfalcato@suse.de, Jason@zx2c4.com, shuah@kernel.org
Subject: Re: [PATCH v4 2/3] selftests/mm: verify droppable mappings cannot be locked
Date: Thu, 16 Apr 2026 10:41:31 +0200 [thread overview]
Message-ID: <d148375f-fe17-4f28-aec6-9732058fc3ab@kernel.org> (raw)
In-Reply-To: <20260416033939.49981-3-anthony.yznaga@oracle.com>
On 4/16/26 05:39, Anthony Yznaga wrote:
> For configs that support MAP_DROPPABLE verify that a mapping created
> with MAP_DROPPABLE cannot be locked via mlock(), and that it will not
> be locked if it's created after mlockall(MCL_FUTURE).
>
> Signed-off-by: Anthony Yznaga <anthony.yznaga@oracle.com>
> Acked-by: David Hildenbrand (Arm) <david@kernel.org>
> ---
LGTM, thanks!
--
Cheers,
David
next prev parent reply other threads:[~2026-04-16 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 3:39 [PATCH v4 0/3] fix MAP_DROPPABLE not supported errno Anthony Yznaga
2026-04-16 3:39 ` [PATCH v4 1/3] mm: fix mmap errno value when MAP_DROPPABLE is not supported Anthony Yznaga
2026-04-16 3:39 ` [PATCH v4 2/3] selftests/mm: verify droppable mappings cannot be locked Anthony Yznaga
2026-04-16 8:41 ` David Hildenbrand (Arm) [this message]
2026-04-16 3:39 ` [PATCH v4 3/3] selftests/mm: run the MAP_DROPPABLE selftest Anthony Yznaga
2026-04-16 8:39 ` 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=d148375f-fe17-4f28-aec6-9732058fc3ab@kernel.org \
--to=david@kernel.org \
--cc=Jason@zx2c4.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=anthony.yznaga@oracle.com \
--cc=jannh@google.com \
--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=pfalcato@suse.de \
--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