On 03/07, Matthew Wilcox (Oracle) wrote: > I was planning on sending this next cycle, but maybe there's time to > squeeze these patches into the upcoming merge window? > > f2fs already implements writepages and migrate_folio for all three > address_space_operations, so either ->writepage will never be called (by > migration) or it will only be harmful (if called from pageout()). My tree sitting on [1] doesn't have mm-next, which looks difficult to test this series for test alone. Matthew, can you point which patches I need to apply in mm along with this for test? [1] f286757b644c "Merge tag 'timers-urgent-2025-02-03' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip" > > The only remaining filesystem with ->writepage defined in next-20250307 > is vboxsf, so the concept of removing ->writepage is well proven. I > have some follow-up patches which simplify f2fs writeback afterwards, > but I think we can postpone them to next cycle. > > See > https://lore.kernel.org/linux-fsdevel/20250307135414.2987755-1-willy@xxxxxxxxxxxxx/ > for where we're going; the first four patches in that series are the > same as the four patches in this series, and I've split them out here > for your convenience. > > Matthew Wilcox (Oracle) (4): > f2fs: Remove check for ->writepage > f2fs: Remove f2fs_write_data_page() > f2fs: Remove f2fs_write_meta_page() > f2fs: Remove f2fs_write_node_page() > > fs/f2fs/checkpoint.c | 7 ------- > fs/f2fs/data.c | 28 ---------------------------- > fs/f2fs/node.c | 8 -------- > 3 files changed, 43 deletions(-) > > -- > 2.47.2
