Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Daehyeon Ko <4ncienth@gmail.com>,
	stable@vger.kernel.org,
	 Andrew Morton <akpm@linux-foundation.org>,
	Mike Rapoport <rppt@kernel.org>,
	 "Liam R. Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	 Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
	 Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	 "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	 Jesper Dangaard Brouer <hawk@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	 Stanislav Fomichev <sdf@fomichev.me>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	 Hagen Paul Pfeifer <hagen@jauu.net>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH v2] mm/secretmem: properly account locked pages
Date: Wed, 26 Aug 2026 17:18:25 +0100	[thread overview]
Message-ID: <ao8RZlK6mBa-oNGh@gremlin> (raw)
In-Reply-To: <ao13TmFVVpsv0zO4@gremlin>

On Tue, Aug 25, 2026 at 12:18:20PM +0100, Lorenzo Stoakes (ARM) wrote:
> > Can we split off the selftest changes? This stable patch is already pretty big.
>
> Yeah I can do! I seem to recall people wanting tests backported too hence
> the change.
>
> >
> > I'd assume the changes to the selftests are not required just to get if fixed,
> > because the changes should not be breaking existing user space (and cosnequently
> > existing selftests).
>
> Yup confirmed locally that the changes don't break the tests.

Correction - somehow I was working with an incorrect version of the test
file or kernel locally, but the tests do fail with this patch, that's
because it only seems to be asserting the mlock_future_ok() check which the
patch removes.

I think the easiest resolution is just to remove the test for the purposes
of the backports and reintroduce the improved test as a separate patch,
will do this.

--
Cheers, Lorenzo


  parent reply	other threads:[~2026-08-26 16:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 19:14 [PATCH v2] mm/secretmem: properly account locked pages Lorenzo Stoakes (ARM)
2026-08-24 13:21 ` Mike Rapoport
2026-08-25 10:50 ` David Hildenbrand (Arm)
2026-08-25 11:18   ` Lorenzo Stoakes (ARM)
2026-08-25 12:56     ` David Hildenbrand (Arm)
2026-08-26 16:18     ` Lorenzo Stoakes (ARM) [this message]
2026-08-26  1:39 ` Daehyeon Ko
2026-08-26  7:57   ` Lorenzo Stoakes (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=ao8RZlK6mBa-oNGh@gremlin \
    --to=ljs@kernel.org \
    --cc=4ncienth@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=david@kernel.org \
    --cc=hagen@jauu.net \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=netdev@vger.kernel.org \
    --cc=rppt@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=stable@vger.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