linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 David Hildenbrand <david@redhat.com>,
	"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>,
	 Jan Kara <jack@suse.cz>, Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v2 1/3] mm: introduce new .mmap_prepare() file callback
Date: Tue, 13 May 2025 09:29:31 +0200	[thread overview]
Message-ID: <20250513-trasse-flugobjekt-22ea7f851118@brauner> (raw)
In-Reply-To: <b33f05e8-9c5b-4be0-977d-005ca525d1db@lucifer.local>

On Mon, May 12, 2025 at 12:31:34PM +0100, Lorenzo Stoakes wrote:
> On Mon, May 12, 2025 at 11:24:06AM +0200, Christian Brauner wrote:
> > On Fri, May 09, 2025 at 01:13:34PM +0100, Lorenzo Stoakes wrote:
> 
> [snip]
> 
> > > diff --git a/include/linux/fs.h b/include/linux/fs.h
> > > index 016b0fe1536e..e2721a1ff13d 100644
> > > --- a/include/linux/fs.h
> > > +++ b/include/linux/fs.h
> 
> [snip]
> 
> > >  static inline int call_mmap(struct file *file, struct vm_area_struct *vma)
> > >  {
> > > +	if (WARN_ON_ONCE(file->f_op->mmap_prepare))
> > > +		return -EINVAL;
> > > +
> > >  	return file->f_op->mmap(file, vma);
> > >  }
> > >
> > > +static inline int __call_mmap_prepare(struct file *file,
> > > +		struct vm_area_desc *desc)
> > > +{
> > > +	return file->f_op->mmap_prepare(desc);
> > > +}
> >
> > nit: I would prefer if we could rename this to vfs_mmap() and
> > vfs_mmap_prepare() as this is in line with all the other vfs related
> > helpers we expose.
> >
> 
> Happy to do it, but:
> 
> call_mmap() is already invoked in a bunch of places, so kinda falls outside this
> series (+ would touch a bunch of unrelated files), would you mind if I sent that
> separately?

Sure, that's fine.


  reply	other threads:[~2025-05-13  7:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 12:13 [PATCH v2 0/3] eliminate mmap() retry merge, add .mmap_prepare hook Lorenzo Stoakes
2025-05-09 12:13 ` [PATCH v2 1/3] mm: introduce new .mmap_prepare() file callback Lorenzo Stoakes
2025-05-12  9:24   ` Christian Brauner
2025-05-12 11:31     ` Lorenzo Stoakes
2025-05-13  7:29       ` Christian Brauner [this message]
2025-05-12 13:37   ` Vlastimil Babka
2025-05-13  9:01   ` David Hildenbrand
2025-05-13  9:32     ` Lorenzo Stoakes
2025-05-13 13:25       ` David Hildenbrand
2025-05-13 15:31         ` Suren Baghdasaryan
2025-05-13 13:22   ` Liam R. Howlett
2025-05-14  9:04   ` Pedro Falcato
2025-05-14  9:12     ` Lorenzo Stoakes
2025-05-14 10:01       ` Pedro Falcato
2025-05-14 10:14         ` Lorenzo Stoakes
2025-05-09 12:13 ` [PATCH v2 2/3] mm: secretmem: convert to .mmap_prepare() hook Lorenzo Stoakes
2025-05-12 13:41   ` Vlastimil Babka
2025-05-13 13:23   ` Liam R. Howlett
2025-05-13 15:32     ` Suren Baghdasaryan
2025-05-09 12:13 ` [PATCH v2 3/3] mm/vma: remove mmap() retry merge Lorenzo Stoakes
2025-05-12 13:44   ` Vlastimil Babka
2025-05-13 13:25   ` Liam R. Howlett
2025-05-13 15:38     ` Suren Baghdasaryan

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=20250513-trasse-flugobjekt-22ea7f851118@brauner \
    --to=brauner@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.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=lorenzo.stoakes@oracle.com \
    --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