Re: [PATCH 00/10] convert the majority of file systems to mmap_prepare
Jeff Layton <[email protected]> Tue, 17 Jun 2025 09:45:32 -0400
| Newsgroups | gmane.linux.kernel.aio.general,gmane.linux.block,gmane.linux.kernel,gmane.comp.freedesktop.xorg.drivers.intel,gmane.comp.video.dri.devel,gmane.linux.file-systems,gmane.linux.file-systems.union,gmane.linux.kernel.mm,gmane.comp.file-systems.btrfs,gmane.comp.file-systems.ceph.devel,gmane.comp.file-systems.coda.general,gmane.comp.file-systems.ecryptfs.general,gmane.comp.file-systems.ext4,gmane.linux.file-systems.f2fs,gmane.linux.uml.devel,gmane.linux.drivers.mtd,gmane.linux.nfs,gmane.comp.file-systems.nilfs.user,gmane.linux.hardware.karma.devel,gmane.linux.kernel.cifs,gmane.network.samba.internals |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 2025-06-16 at 21:41 +0100, Al Viro wrote: > On Mon, Jun 16, 2025 at 08:33:19PM +0100, Lorenzo Stoakes wrote: > > 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. -- Jeff Layton <[email protected]> -- To unsubscribe, send a message with 'unsubscribe linux-aio' in the body to [email protected]. For more info on Linux AIO, see: http://www.kvack.org/aio/ Don't email: <a href=mailto:"[email protected]">[email protected]</a>