Thread (50 messages) 50 messages, 18 authors, 2025-08-01

Re: [PATCH 00/10] convert the majority of file systems to mmap_prepare

From: Lorenzo Stoakes <hidden>
Date: 2025-06-17 13:48:01
Also in: ceph-devel, dri-devel, intel-gfx, linux-bcachefs, linux-block, linux-btrfs, linux-cifs, linux-f2fs-devel, linux-fsdevel, linux-mm, linux-nfs, linux-um, linux-unionfs, linux-xfs, lkml, ntfs3, nvdimm, ocfs2-devel, v9fs

On Tue, Jun 17, 2025 at 09:45:32AM -0400, Jeff Layton wrote:
On Mon, 2025-06-16 at 21:41 +0100, Al Viro wrote:
quoted
On Mon, Jun 16, 2025 at 08:33:19PM +0100, Lorenzo Stoakes wrote:
quoted
REVIEWER'S NOTES
================

I am basing this on the mm-new branch in Andrew's tree, so let me know if I
should rebase anything here. Given the mm bits touched I did think perhaps
we should take it through the mm tree, however it may be more sensible to
take it through an fs tree - let me know!

Apologies for the noise/churn, but there are some prerequisite steps here
that inform an ordering - "fs: consistently use file_has_valid_mmap_hooks()
helper" being especially critical, and so I put the bulk of the work in the
same series.

Let me know if there's anything I can do to make life easier here.
Documentation/filesystems/porting.rst?
Also, an entry for ->mmap_prepare in Documentation/filesystems/vfs.rst
would be good.

I went there first to understand what the requirements of mmap_prepare
are, but there is nothing.
Ack, on it.
--
Jeff Layton [off-list ref]
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help