On Wed, Jan 18, 2023 at 06:30:20PM +0100, Christoph Hellwig wrote:> Hi all, > > this series removes most users of the write_one_page API. These helpers > internally call ->writepage which we are gradually removing from the > kernel. > > Changes since v2: > - more minix error handling fixes > > Changes since v1: > - drop the btrfs changes (queue up in the btrfs tree) > - drop the finaly move to jfs (can't be done without the btrfs patches) > - fix the existing minix code to properly propagate errorsGrabbed. I'll split that into per-fs branches (and synchronize wrt fixes), fold the kmap_local stuff into that and push out.
On Wed, Jan 18, 2023 at 09:23:37PM +0000, Al Viro wrote:> On Wed, Jan 18, 2023 at 06:30:20PM +0100, Christoph Hellwig wrote: > > Hi all, > > > > this series removes most users of the write_one_page API. These helpers > > internally call ->writepage which we are gradually removing from the > > kernel. > > > > Changes since v2: > > - more minix error handling fixes > > > > Changes since v1: > > - drop the btrfs changes (queue up in the btrfs tree) > > - drop the finaly move to jfs (can't be done without the btrfs patches) > > - fix the existing minix code to properly propagate errors > > Grabbed. I'll split that into per-fs branches (and synchronize wrt > fixes), fold the kmap_local stuff into that and push out.BTW, do you have the check for minix_delete_entry() failure when called from minix_rename() anywhere in your tree? I don't see that in this series; I'm adding the trivial fix, hopefully that won't end up creating conflicts...
Apparently Analagous Threads
- remove most callers of write_one_page v3
- remove most callers of write_one_page v3
- remove most callers of write_one_page v4
- [PATCH 2/3] ocfs2: don't use write_one_page in ocfs2_duplicate_clusters_by_page
- + ocfs2-dont-use-write_one_page-in-ocfs2_duplicate_clusters_by_page.patch added to mm-unstable branch