From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Peter Xu <peterx@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>,
Rik van Riel <riel@surriel.com>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 04/10] mm/mremap: cleanup post-processing stage of mremap
Date: Thu, 10 Jul 2025 16:28:58 +0100 [thread overview]
Message-ID: <d3facf9d-9a65-401b-880e-4e321b6b4794@lucifer.local> (raw)
In-Reply-To: <277aa9f4-ddb7-4f34-ad15-a98888108cb5@suse.cz>
On Thu, Jul 10, 2025 at 03:49:09PM +0200, Vlastimil Babka wrote:
> On 7/7/25 07:27, Lorenzo Stoakes wrote:
> > Separate out the uffd bits so it clear's what's happening.
> >
> > Don't bother setting vrm->mmap_locked after unlocking, because after this
> > we are done anyway.
> >
> > The only time we drop the mmap lock is on VMA shrink, at which point
> > vrm->new_len will be < vrm->old_len and the operation will not be performed
> > anyway, so move this code out of the if (vrm->mmap_locked) block.
> >
> > All addresses returned by mremap() are page-aligned, so the
> > offset_in_page() check on ret seems only to be incorrectly trying to detect
>
> "incorrectly" to me implies there's a bug. But AFAIU there's not, so maybe
> e.g. "inappropriately"?
>
> > whether an error occurred - explicitly check for this.
> >
> > No functional change intended.
> >
> > Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>
> Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
Thanks! :)
>
> Just a nit:
>
> > ---
> > mm/mremap.c | 22 +++++++++++++---------
> > 1 file changed, 13 insertions(+), 9 deletions(-)
> >
> > diff --git a/mm/mremap.c b/mm/mremap.c
> > index 60eb0ac8634b..660bdb75e2f9 100644
> > --- a/mm/mremap.c
> > +++ b/mm/mremap.c
> > @@ -1729,6 +1729,15 @@ static int check_prep_vma(struct vma_remap_struct *vrm)
> > return 0;
> > }
> >
> > +static void notify_uffd(struct vma_remap_struct *vrm, unsigned long ret)
>
> "ret" not "res"? :) Or actually why not name it for what it is,
> mremap_userfaultfd_complete() names the parameter "to". Maybe to_addr or
> new_addr?
Later in the series we eliminate this as you've seen, but still worth fixign up
I think, will do on respin!
>
> > +{
> > + struct mm_struct *mm = current->mm;
> > +
> > + userfaultfd_unmap_complete(mm, vrm->uf_unmap_early);
> > + mremap_userfaultfd_complete(vrm->uf, vrm->addr, ret, vrm->old_len);
> > + userfaultfd_unmap_complete(mm, vrm->uf_unmap);
> > +}
> > +
> > static unsigned long do_mremap(struct vma_remap_struct *vrm)
> > {
> > struct mm_struct *mm = current->mm;
> > @@ -1754,18 +1763,13 @@ static unsigned long do_mremap(struct vma_remap_struct *vrm)
> > res = vrm_implies_new_addr(vrm) ? mremap_to(vrm) : mremap_at(vrm);
> >
> > out:
> > - if (vrm->mmap_locked) {
> > + if (vrm->mmap_locked)
> > mmap_write_unlock(mm);
> > - vrm->mmap_locked = false;
> > -
> > - if (!offset_in_page(res) && vrm->mlocked && vrm->new_len > vrm->old_len)
> > - mm_populate(vrm->new_addr + vrm->old_len, vrm->delta);
> > - }
> >
> > - userfaultfd_unmap_complete(mm, vrm->uf_unmap_early);
> > - mremap_userfaultfd_complete(vrm->uf, vrm->addr, res, vrm->old_len);
> > - userfaultfd_unmap_complete(mm, vrm->uf_unmap);
> > + if (!IS_ERR_VALUE(res) && vrm->mlocked && vrm->new_len > vrm->old_len)
> > + mm_populate(vrm->new_addr + vrm->old_len, vrm->delta);
> >
> > + notify_uffd(vrm, res);
> > return res;
> > }
> >
>
next prev parent reply other threads:[~2025-07-10 15:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 5:27 [PATCH 00/10] mm/mremap: permit mremap() move of multiple VMAs Lorenzo Stoakes
2025-07-07 5:27 ` [PATCH 01/10] mm/mremap: perform some simple cleanups Lorenzo Stoakes
2025-07-10 11:09 ` Vlastimil Babka
2025-07-07 5:27 ` [PATCH 02/10] mm/mremap: refactor initial parameter sanity checks Lorenzo Stoakes
2025-07-10 11:38 ` Vlastimil Babka
2025-07-07 5:27 ` [PATCH 03/10] mm/mremap: put VMA check and prep logic into helper function Lorenzo Stoakes
2025-07-10 13:10 ` Vlastimil Babka
2025-07-07 5:27 ` [PATCH 04/10] mm/mremap: cleanup post-processing stage of mremap Lorenzo Stoakes
2025-07-10 13:49 ` Vlastimil Babka
2025-07-10 15:28 ` Lorenzo Stoakes [this message]
2025-07-07 5:27 ` [PATCH 05/10] mm/mremap: use an explicit uffd failure path for mremap Lorenzo Stoakes
2025-07-07 7:56 ` kernel test robot
2025-07-07 10:13 ` Lorenzo Stoakes
2025-07-07 10:20 ` Lorenzo Stoakes
2025-07-10 14:24 ` Vlastimil Babka
2025-07-07 5:27 ` [PATCH 06/10] mm/mremap: check remap conditions earlier Lorenzo Stoakes
2025-07-10 14:36 ` Vlastimil Babka
2025-07-07 5:27 ` [PATCH 07/10] mm/mremap: move remap_is_valid() into check_prep_vma() Lorenzo Stoakes
2025-07-10 14:44 ` Vlastimil Babka
2025-07-07 5:27 ` [PATCH 08/10] mm/mremap: clean up mlock populate behaviour Lorenzo Stoakes
2025-07-10 14:47 ` Vlastimil Babka
2025-07-07 5:27 ` [PATCH 09/10] mm/mremap: permit mremap() move of multiple VMAs Lorenzo Stoakes
2025-07-09 18:13 ` Liam R. Howlett
2025-07-10 10:41 ` Lorenzo Stoakes
2025-07-11 8:17 ` Mark Brown
2025-07-11 8:22 ` Mark Brown
2025-07-11 8:31 ` Lorenzo Stoakes
2025-07-07 5:27 ` [PATCH 10/10] tools/testing/selftests: extend mremap_test to test multi-VMA mremap Lorenzo Stoakes
2025-07-07 6:12 ` [PATCH 00/10] mm/mremap: permit mremap() move of multiple VMAs Hugh Dickins
2025-07-07 10:31 ` Lorenzo Stoakes
2025-07-07 10:34 ` Lorenzo Stoakes
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=d3facf9d-9a65-401b-880e-4e321b6b4794@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=pfalcato@suse.de \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).