From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: linux-fsdevel@vger.kernel.org
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
cluster-devel@redhat.com, linux-mtd@lists.infradead.org,
linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] Unify filler_t and read_folio
Date: Mon, 2 May 2022 06:41:56 +0100 [thread overview]
Message-ID: <20220502054159.3471078-1-willy@infradead.org> (raw)
I realised there was no good reason for any of the three filesystems which
actually use read_cache_page() to pass in something that wasn't a struct
file pointer. Indeed, it made each of them more complex. These aren't
filesystems I test regularly, so please scrutinise carefully. This is
on top of the read_folio() patchset that I posted recently and can be
found at git://git.infradead.org/users/willy/pagecache.git for-next
Matthew Wilcox (Oracle) (3):
jffs2: Pass the file pointer to jffs2_do_readpage_unlock()
nfs: Pass the file pointer to nfs_symlink_filler()
fs: Change the type of filler_t
fs/gfs2/aops.c | 29 +++++++++++------------------
fs/jffs2/file.c | 9 ++++-----
fs/jffs2/gc.c | 2 +-
fs/jffs2/os-linux.h | 2 +-
fs/nfs/symlink.c | 16 ++++++++--------
include/linux/pagemap.h | 6 +++---
mm/filemap.c | 40 ++++++++++++++++++++--------------------
7 files changed, 48 insertions(+), 56 deletions(-)
--
2.34.1
next reply other threads:[~2022-05-02 5:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 5:41 Matthew Wilcox (Oracle) [this message]
2022-05-02 5:41 ` [PATCH 1/3] jffs2: Pass the file pointer to jffs2_do_readpage_unlock() Matthew Wilcox (Oracle)
2022-05-03 14:18 ` Christoph Hellwig
2022-05-02 5:41 ` [PATCH 2/3] nfs: Pass the file pointer to nfs_symlink_filler() Matthew Wilcox (Oracle)
2022-05-03 14:21 ` Christoph Hellwig
2022-05-02 5:41 ` [PATCH 3/3] fs: Change the type of filler_t Matthew Wilcox (Oracle)
2022-05-03 14:23 ` Christoph Hellwig
2022-05-08 19:06 ` Matthew Wilcox
2022-05-03 22:07 ` [Cluster-devel] " Andreas Gruenbacher
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=20220502054159.3471078-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=cluster-devel@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.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;
as well as URLs for NNTP newsgroup(s).