From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: David Hildenbrand <david@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH 2/3] mm: secretmem: convert to .mmap_prepare() hook
Date: Fri, 9 May 2025 11:38:43 +0100 [thread overview]
Message-ID: <dcf6fec6-a4ee-4ac9-9796-c5fd89e51228@lucifer.local> (raw)
In-Reply-To: <708b6b1b-54a0-43b8-b6ec-a2dbb089d432@redhat.com>
On Fri, May 09, 2025 at 11:45:16AM +0200, David Hildenbrand wrote:
> On 07.05.25 13:03, Lorenzo Stoakes wrote:
> > Secretmem has a simple .mmap() hook which is easily converted to the new
> > .mmap_prepare() callback.
> >
> > Importantly, it's a rare instance of an driver that manipulates a VMA which
> > is mergeable (that is, not a VM_SPECIAL mapping) while also adjusting VMA
> > flags which may adjust mergeability, meaning the retry merge logic might
> > impact whether or not the VMA is merged.
> >
> > By using .mmap_prepare() there's no longer any need to retry the merge
> > later as we can simply set the correct flags from the start.
> >
> > This change therefore allows us to remove the retry merge logic in a
> > subsequent commit.
> >
> > Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> > ---
> > mm/secretmem.c | 14 +++++++-------
> > 1 file changed, 7 insertions(+), 7 deletions(-)
> >
> > diff --git a/mm/secretmem.c b/mm/secretmem.c
> > index 1b0a214ee558..f98cf3654974 100644
> > --- a/mm/secretmem.c
> > +++ b/mm/secretmem.c
> > @@ -120,18 +120,18 @@ static int secretmem_release(struct inode *inode, struct file *file)
> > return 0;
> > }
> > -static int secretmem_mmap(struct file *file, struct vm_area_struct *vma)
> > +static int secretmem_mmap_prepare(struct vm_area_desc *desc)
> > {
> > - unsigned long len = vma->vm_end - vma->vm_start;
> > + unsigned long len = desc->end - desc->start;
>
> I'd have marked that const while touching it.
Will fix up on respin.
>
> > - if ((vma->vm_flags & (VM_SHARED | VM_MAYSHARE)) == 0)
> > + if ((desc->vm_flags & (VM_SHARED | VM_MAYSHARE)) == 0)
> > return -EINVAL;
> > - if (!mlock_future_ok(vma->vm_mm, vma->vm_flags | VM_LOCKED, len))
> > + if (!mlock_future_ok(desc->mm, desc->vm_flags | VM_LOCKED, len))
> > return -EAGAIN;
> > - vm_flags_set(vma, VM_LOCKED | VM_DONTDUMP);
> > - vma->vm_ops = &secretmem_vm_ops;
> > + desc->vm_flags |= VM_LOCKED | VM_DONTDUMP;
> > + desc->vm_ops = &secretmem_vm_ops;
>
> Yeah, that looks much better.
>
> Acked-by: David Hildenbrand <david@redhat.com>
Thanks!
>
> --
> Cheers,
>
> David / dhildenb
>
next prev parent reply other threads:[~2025-05-09 10:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 11:03 [PATCH 0/3] eliminate mmap() retry merge, add .mmap_prepare hook Lorenzo Stoakes
2025-05-07 11:03 ` [PATCH 1/3] mm: introduce new .mmap_prepare() file callback Lorenzo Stoakes
2025-05-09 10:00 ` David Hildenbrand
2025-05-09 10:45 ` Lorenzo Stoakes
2025-05-09 10:51 ` David Hildenbrand
2025-05-09 10:57 ` Lorenzo Stoakes
2025-05-09 10:59 ` David Hildenbrand
2025-05-07 11:03 ` [PATCH 2/3] mm: secretmem: convert to .mmap_prepare() hook Lorenzo Stoakes
2025-05-09 9:45 ` David Hildenbrand
2025-05-09 10:38 ` Lorenzo Stoakes [this message]
2025-05-07 11:03 ` [PATCH 3/3] mm/vma: remove mmap() retry merge Lorenzo Stoakes
2025-05-09 9:45 ` David Hildenbrand
2025-05-09 10:38 ` 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=dcf6fec6-a4ee-4ac9-9796-c5fd89e51228@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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