It was decided to remove the page_endio() as per the previous RFC discussion[1] of this series and move that functionality into the caller itself. One of the side benefit of doing that is the callers have been modified to directly work on folios as page_endio() already worked on folios. mpage changes were tested with a simple boot testing. orangefs was tested by Mike Marshall (No code changes since he tested). A basic testing was performed for the zram changes with fio and writeback to a backing device. Changes since v1: - Always chain the IO to the parent as it can never be NULL (Minchan) - Added reviewed and tested by tags Changes since RFC 2[2]: - Call bio_put in zram bio end io handler (Still not Acked by hch[3]) - Call folio_set_error in mpage read endio error path (Willy) - Directly call folio->mapping in mpage write endio error path (Willy) [1] https://lore.kernel.org/linux-mm/ZBHcl8Pz2ULb4RGD@xxxxxxxxxxxxx/ [2] https://lore.kernel.org/linux-mm/20230322135013.197076-1-p.raghav@xxxxxxxxxxx/ [3] https://lore.kernel.org/linux-mm/8adb0770-6124-e11f-2551-6582db27ed32@xxxxxxxxxxx/ Pankaj Raghav (5): zram: always chain bio to the parent in read_from_bdev_async orangefs: use folios in orangefs_readahead mpage: split bi_end_io callback for reads and writes mpage: use folios in bio end_io handler filemap: remove page_endio() drivers/block/zram/zram_drv.c | 16 +++------------ fs/mpage.c | 38 +++++++++++++++++++++++++++-------- fs/orangefs/inode.c | 9 +++++---- include/linux/pagemap.h | 2 -- mm/filemap.c | 30 --------------------------- 5 files changed, 38 insertions(+), 57 deletions(-) -- 2.34.1
