From: Andrew Morton <akpm@linux-foundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: Anthony Yznaga <anthony.yznaga@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, david@kernel.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 v2 2/2] selftests/mm: verify droppable mappings cannot be locked
Date: Tue, 31 Mar 2026 14:17:14 -0700 [thread overview]
Message-ID: <20260331141714.b2f4e41b494060e55610a5f3@linux-foundation.org> (raw)
In-Reply-To: <52bec9ea-5627-4ea2-8f27-f1729957fa47@sirena.org.uk>
On Tue, 31 Mar 2026 14:17:50 +0100 Mark Brown <broonie@kernel.org> wrote:
> On Tue, Mar 10, 2026 at 08:58:21AM -0700, Anthony Yznaga wrote:
>
> > 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).
>
> I'm seeing a regression in -next on 32 bit arm which bisects to this
> patch:
Cool, thanks.
> ...
>
> All these failures which cause the entire test program to immediately
> die seem exceessively strong...
Well, is the test code incorrect, or is the patch which it's testing
incorrect? That's 5435ba164b0d ("mm: prevent droppable mappings from
being locked")?
5435ba164b0d is presently in mm-stable, cc:stable@vger.kernel.org.
next prev parent reply other threads:[~2026-03-31 21:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 15:58 [PATCH v2 1/2] mm: prevent droppable mappings from being locked Anthony Yznaga
2026-03-10 15:58 ` [PATCH v2 2/2] selftests/mm: verify droppable mappings cannot be locked Anthony Yznaga
2026-03-11 9:56 ` Pedro Falcato
2026-03-11 11:25 ` Lorenzo Stoakes (Oracle)
2026-03-31 13:17 ` Mark Brown
2026-03-31 21:17 ` Andrew Morton [this message]
2026-04-01 11:17 ` Mark Brown
2026-04-01 20:27 ` Andrew Morton
2026-03-31 22:45 ` anthony.yznaga
2026-03-11 9:27 ` [PATCH v2 1/2] mm: prevent droppable mappings from being locked David Hildenbrand (Arm)
2026-03-12 2:01 ` anthony.yznaga
2026-03-12 8:55 ` David Hildenbrand (Arm)
2026-03-11 9:54 ` Pedro Falcato
2026-03-11 10:36 ` Lorenzo Stoakes (Oracle)
2026-03-11 17:14 ` Andrew Morton
2026-03-12 2:16 ` anthony.yznaga
2026-03-12 8:32 ` David Hildenbrand (Arm)
2026-04-02 23:59 [PATCH v2 0/2] fix MAP_DROPPABLE not supported errno Anthony Yznaga
2026-04-02 23:59 ` [PATCH v2 2/2] selftests/mm: verify droppable mappings cannot be locked Anthony Yznaga
2026-04-03 19:31 ` Andrew Morton
2026-04-08 20:35 ` anthony.yznaga
2026-04-08 21:02 ` Andrew Morton
2026-04-08 22:26 ` anthony.yznaga
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=20260331141714.b2f4e41b494060e55610a5f3@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Jason@zx2c4.com \
--cc=Liam.Howlett@oracle.com \
--cc=anthony.yznaga@oracle.com \
--cc=broonie@kernel.org \
--cc=david@kernel.org \
--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