summaryrefslogtreecommitdiffstats
path: root/mm/swapfile.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2022-05-10 03:20:47 +0200
committerakpm <akpm@linux-foundation.org>2022-05-10 03:20:47 +0200
commit4c4a763406ef903b78334bd2ccea168d2f7a741a (patch)
tree9dff8e975ae6375ccbc82d72b028d523eadefffa /mm/swapfile.c
parentmm: create new mm/swap.h header file (diff)
downloadlinux-4c4a763406ef903b78334bd2ccea168d2f7a741a.tar.xz
linux-4c4a763406ef903b78334bd2ccea168d2f7a741a.zip
mm: drop swap_dirty_folio
folios that are written to swap are owned by the MM subsystem - not any filesystem. When such a folio is passed to a filesystem to be written out to a swap-file, the filesystem handles the data, but the folio itself does not belong to the filesystem. So calling the filesystem's ->dirty_folio() address_space operation makes no sense. This is for folios in the given address space, and a folio to be written to swap does not exist in the given address space. So drop swap_dirty_folio() which calls the address-space's ->dirty_folio(), and always use noop_dirty_folio(), which is appropriate for folios being swapped out. Link: https://lkml.kernel.org/r/164859778123.29473.6900942583784889976.stgit@noble.brown Signed-off-by: NeilBrown <neilb@suse.de> Reviewed-by: Christoph Hellwig <hch@lst.de> Tested-by: David Howells <dhowells@redhat.com> Tested-by: Geert Uytterhoeven <geert+renesas@glider.be> Cc: Hugh Dickins <hughd@google.com> Cc: Mel Gorman <mgorman@techsingularity.net> Cc: Trond Myklebust <trond.myklebust@hammerspace.com> Cc: Miaohe Lin <linmiaohe@huawei.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm/swapfile.c')
0 files changed, 0 insertions, 0 deletions