fuse-drop-usage-of-folio_index.patch removed from -mm tree
The quilt patch titled
Subject: fuse: drop usage of folio_index
has been removed from the -mm tree. Its filename was
fuse-drop-usage-of-folio_index.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Kairui Song <[email protected]>
Subject: fuse: drop usage of folio_index
Date: Thu, 1 May 2025 02:10:47 +0800
Patch series "mm, swap: clean up swap cache mapping helper", v3.
This series removes usage of folio_index usage in fs/, and remove swap cache checking in folio_contains.
Currently, the swap cache is already no longer directly exposed to fs, and swap cache will be more different from page cache. Clean up the helpers first to simplify the code and eliminate the helpers used for resolving circular header dependency issue between filemap and swap headers, and prepare for further changes.
This patch (of 6):
folio_index is only needed for mixed usage of page cache and swap cache, for pure page cache usage, the caller can just use folio->index instead.
It can't be a swap cache folio here. Swap mapping may only call into fs through swap_rw but fuse does not use that method for SWAP.
---
fs/fuse/file.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/fuse/file.c renamed from fs/fuse/file.c~fuse-drop-usage-of-folio_index +2 -2
@@ -487,7 +487,7 @@ static inline bool fuse_folio_is_writeba struct folio *folio) {pgoff_t last =folio_next_index (folio) -1 ; -return fuse_range_is_writeback (inode,folio_index (folio), last); +return fuse_range_is_writeback (inode, folio->index, last); } static void fuse_wait_on_folio_writeback(struct inode *inode,
@@ -2349,7 +2349,7 @@ static bool fuse_writepage_need_send(strreturn true;/* Discontinuity */ -if (data->orig_folios[ap->num_folios -1 ]->index +1 !=folio_index (folio)) +if (data->orig_folios[ap->num_folios -1 ]->index +1 != folio->index)return true;/* Need to grow the pages array? If so, did the expansion fail? */
_
Patches currently in -mm which might be from [email protected] are