From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: Christian Brauner <christian@brauner.io>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Jan Kara <jack@suse.cz>, Gao Xiang <xiang@kernel.org>,
Chao Yu <chao@kernel.org>, "Theodore Tso" <tytso@mit.edu>,
Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>,
Namjae Jeon <linkinjeon@kernel.org>,
Hyunchul Lee <hyc.lee@gmail.com>,
Phillip Lougher <phillip@squashfs.org.uk>,
linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-nfs@vger.kernel.org,
ntfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH 0/9] Remove FGP_NOFS
Date: Sun, 30 Aug 2026 05:18:47 +0100 [thread overview]
Message-ID: <20260830041901.2668-1-willy@infradead.org> (raw)
There is broad agreement that we should eliminate __GFP_FS in favour of
using memalloc_nofs_save(). This is a small step in that direction by
getting rid of FGP_NOFS. It's also a nice simplification in its own right.
I added the documentation improvement at the start of this series, not
because anything depends on that (obviously it doesn't), but because
I thought the existing documentation was rather MM centric and it needs
to be FS centric. Hopefully the cc'd filesystem maintainers will have
the chance to look at patch 1 and see if it makes sense to them.
There's a few different solutions here:
- Filesystems specifying both FGP_NOWAIT and FGP_NOFS. If you're not
waiting, it doesn't matter if you're allowed to reclaim from FS
context or not, you're just not doing reclaim.
- We're already under memalloc_nofs.
- We can prove that the MM should be allowed to reclaim from
filesystem memory (and so specifying FGP_NOFS was wrong).
- We can add a call to memalloc_nofs_save().
Matthew Wilcox (Oracle) (9):
mm: Improve memalloc_nofs_save() documentation
ext4: Remove uses of FGP_NOFS
erofs: Remove redundant FGP_NOFS
nfs: Remove redundant FGP_NOFS
ntfs: Remove FGP_NOFS from __ntfs_inode_resident_attr_pwrite()
ntfs: Remove redundant FGP_NOFS from ntfs_wof_collect_dest()
squashfs: Remove use of FGP_NOFS
filemap: Remove redundant FGP_NOFS
filemap: Remove FGP_NOFS
fs/erofs/internal.h | 2 +-
fs/ext4/inline.c | 6 ++----
fs/nfs/dir.c | 2 +-
fs/ntfs/inode.c | 2 +-
fs/ntfs/wof.c | 7 +++----
fs/squashfs/file.c | 5 ++++-
include/linux/pagemap.h | 12 +++++-------
include/linux/sched/mm.h | 31 +++++++++++++++++++++++--------
mm/filemap.c | 2 --
mm/readahead.c | 14 ++------------
10 files changed, 42 insertions(+), 41 deletions(-)
--
2.47.3
next reply other threads:[~2026-08-30 4:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 4:18 Matthew Wilcox (Oracle) [this message]
2026-08-30 4:18 ` [PATCH 1/9] mm: Improve memalloc_nofs_save() documentation Matthew Wilcox (Oracle)
2026-08-30 4:21 ` sashiko-bot
2026-08-30 4:18 ` [PATCH 2/9] ext4: Remove uses of FGP_NOFS Matthew Wilcox (Oracle)
2026-08-30 4:27 ` sashiko-bot
2026-08-30 4:18 ` [PATCH 3/9] erofs: Remove redundant FGP_NOFS Matthew Wilcox (Oracle)
2026-08-30 4:24 ` sashiko-bot
2026-08-30 4:18 ` [PATCH 4/9] nfs: " Matthew Wilcox (Oracle)
2026-08-30 4:26 ` sashiko-bot
2026-08-30 4:18 ` [PATCH 5/9] ntfs: Remove FGP_NOFS from __ntfs_inode_resident_attr_pwrite() Matthew Wilcox (Oracle)
2026-08-30 4:39 ` sashiko-bot
2026-08-30 4:18 ` [PATCH 6/9] ntfs: Remove redundant FGP_NOFS from ntfs_wof_collect_dest() Matthew Wilcox (Oracle)
2026-08-30 4:25 ` sashiko-bot
2026-08-30 4:18 ` [PATCH 7/9] squashfs: Remove use of FGP_NOFS Matthew Wilcox (Oracle)
2026-08-30 4:33 ` sashiko-bot
2026-08-30 4:18 ` [PATCH 8/9] filemap: Remove redundant FGP_NOFS Matthew Wilcox (Oracle)
2026-08-30 4:25 ` sashiko-bot
2026-08-30 4:18 ` [PATCH 9/9] filemap: Remove FGP_NOFS Matthew Wilcox (Oracle)
2026-08-30 4:27 ` sashiko-bot
2026-08-30 4:32 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260830041901.2668-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=anna@kernel.org \
--cc=chao@kernel.org \
--cc=christian@brauner.io \
--cc=hyc.lee@gmail.com \
--cc=jack@suse.cz \
--cc=linkinjeon@kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ntfs@lists.linux.dev \
--cc=phillip@squashfs.org.uk \
--cc=trondmy@kernel.org \
--cc=tytso@mit.edu \
--cc=xiang@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox