diff options
| author | Hugh Dickins <hughd@google.com> | 2022-05-06 15:22:36 -0400 |
|---|---|---|
| committer | Eric Sandeen <sandeen@sandeen.net> | 2022-05-06 15:22:36 -0400 |
| commit | dabdb3836cea0680b744daae068c7eac24fe1556 (patch) | |
| tree | 093daff58d47dcfad204a57f274db5baaadfdfec | |
| parent | bc4d60eba3f225f7ca1023d1f3b5caafd714813e (diff) | |
| download | xfsprogs-dev-libxfs-5.18-sync.tar.gz | |
mm/fs: delete PF_SWAPWRITElibxfs-5.18-sync
Source kernel commit: b698f0a1773f7df73f2bb4bfe0e597ea1bb3881f
PF_SWAPWRITE has been redundant since v3.2 commit ee72886d8ed5 ("mm:
vmscan: do not writeback filesystem pages in direct reclaim").
Coincidentally, NeilBrown's current patch "remove inode_congested()"
deletes may_write_to_inode(), which appeared to be the one function which
took notice of PF_SWAPWRITE. But if you study the old logic, and the
conditions under which may_write_to_inode() was called, you discover that
flag and function have been pointless for a decade.
Link: https://lkml.kernel.org/r/75e80e7-742d-e3bd-531-614db8961e4@google.com
Signed-off-by: Hugh Dickins <hughd@google.com>
Cc: NeilBrown <neilb@suse.de>
Cc: Jan Kara <jack@suse.de>
Cc: "Darrick J. Wong" <djwong@kernel.org>
Cc: Dave Chinner <david@fromorbit.com>
Cc: Matthew Wilcox <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
| -rw-r--r-- | libxfs/xfs_btree.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/libxfs/xfs_btree.c b/libxfs/xfs_btree.c index 4fe2378e75..18fbe768ed 100644 --- a/libxfs/xfs_btree.c +++ b/libxfs/xfs_btree.c @@ -2815,7 +2815,7 @@ xfs_btree_split_worker( * in any way. */ if (args->kswapd) - new_pflags |= PF_MEMALLOC | PF_SWAPWRITE | PF_KSWAPD; + new_pflags |= PF_MEMALLOC | PF_KSWAPD; current_set_flags_nested(&pflags, new_pflags); xfs_trans_set_context(args->cur->bc_tp); |