From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>,
Brian Geffon <bgeffon@google.com>,
Minchan Kim <minchan@kernel.org>,
Kiryl Shutsemau <kas@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
"Jose A. Perez de Azpillaga" <azpijr@gmail.com>
Subject: Re: [PATCH v2 0/2] mm/mremap: fix two issues with MREMAP_DONTUNMAP
Date: Thu, 1 Oct 2026 09:10:42 +0100 [thread overview]
Message-ID: <ar4VdqHwMRuYdqck@gremlin> (raw)
In-Reply-To: <CAEev2e8TXNwon=Ro27WYvyn-N5j=CenA8pEgLTPerMQtDh2OWw@mail.gmail.com>
On Wed, Sep 30, 2026 at 02:15:16PM -0500, Anirudh Srinivasan wrote:
> On Wed, Sep 30, 2026 at 1:47 PM Lorenzo Stoakes (ARM) <ljs@kernel.org> wrote:
> > mm/mremap.c | 70 ++++++++++++++++++++++++++++++++-----------
> > mm/vma.c | 21 +++++++++++--
> > mm/vma.h | 7 ++++-
> > tools/testing/vma/tests/vma.c | 10 +++----
> > 4 files changed, 81 insertions(+), 27 deletions(-)
>
> Thanks, the selftests are passing now.
>
> Tested-by: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>
Great, thanks for confirming :)
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-10-01 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 18:47 [PATCH v2 0/2] mm/mremap: fix two issues with MREMAP_DONTUNMAP Lorenzo Stoakes (ARM)
2026-09-30 18:47 ` [PATCH v2 1/2] mm/mremap: fix locked_vm leak from MREMAP_DONTUNMAP self-merge Lorenzo Stoakes (ARM)
2026-09-30 18:47 ` [PATCH v2 2/2] mm/mremap: fix locked_vm leak by splitting VMA for MREMAP_DONTUNMAP Lorenzo Stoakes (ARM)
2026-09-30 19:15 ` [PATCH v2 0/2] mm/mremap: fix two issues with MREMAP_DONTUNMAP Anirudh Srinivasan
2026-10-01 8:10 ` Lorenzo Stoakes (ARM) [this message]
2026-09-30 22:21 ` Andrew Morton
2026-10-01 8:05 ` 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=ar4VdqHwMRuYdqck@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=asrinivasan@oss.tenstorrent.com \
--cc=azpijr@gmail.com \
--cc=bgeffon@google.com \
--cc=jannh@google.com \
--cc=kas@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=pfalcato@suse.de \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.