From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] Folio fixes for 5.18
Date: Fri, 1 Apr 2022 19:54:59 +0100 [thread overview]
Message-ID: <YkdKgzil38iyc7rX@casper.infradead.org> (raw)
A mixture of odd changes that didn't quite make it into the original
pull and fixes for things that did. Also the readpages changes had to
wait for the NFS tree to be pulled first.
The following changes since commit d888c83fcec75194a8a48ccd283953bdba7b2550:
fs: fix fd table size alignment properly (2022-03-29 23:29:18 -0700)
are available in the Git repository at:
git://git.infradead.org/users/willy/pagecache.git tags/folio-5.18d
for you to fetch changes up to 5a60542c61f3cce6e5dff2a38c8fb08a852a517b:
btrfs: Remove a use of PAGE_SIZE in btrfs_invalidate_folio() (2022-04-01 14:40:44 -0400)
----------------------------------------------------------------
Filesystem/VFS changes for 5.18, part two
- Remove ->readpages infrastructure
- Remove AOP_FLAG_CONT_EXPAND
- Move read_descriptor_t to networking code
- Pass the iocb to generic_perform_write
- Minor updates to iomap, btrfs, ext4, f2fs, ntfs
----------------------------------------------------------------
Christoph Hellwig (2):
mm: remove the pages argument to read_pages
mm: remove the skip_page argument to read_pages
Matthew Wilcox (Oracle) (13):
readahead: Remove read_cache_pages()
fs: Remove ->readpages address space operation
readahead: Update comments
iomap: Simplify is_partially_uptodate a little
fs: Remove read_actor_t
fs, net: Move read_descriptor_t to net.h
fs: Pass an iocb to generic_perform_write()
filemap: Remove AOP_FLAG_CONT_EXPAND
ext4: Correct ext4_journalled_dirty_folio() conversion
f2fs: Correct f2fs_dirty_data_folio() conversion
f2fs: Get the superblock from the mapping instead of the page
ntfs: Correct mark_ntfs_record_dirty() folio conversion
btrfs: Remove a use of PAGE_SIZE in btrfs_invalidate_folio()
Documentation/filesystems/fsverity.rst | 6 +-
Documentation/filesystems/locking.rst | 6 -
Documentation/filesystems/vfs.rst | 11 --
fs/btrfs/inode.c | 2 +-
fs/btrfs/reflink.c | 4 +-
fs/buffer.c | 3 +-
fs/ceph/file.c | 2 +-
fs/cifs/cifssmb.c | 2 +-
fs/cifs/inode.c | 2 +-
fs/crypto/crypto.c | 2 +-
fs/ext4/file.c | 2 +-
fs/ext4/inode.c | 2 +-
fs/ext4/readpage.c | 2 +-
fs/f2fs/checkpoint.c | 2 +-
fs/f2fs/data.c | 6 +-
fs/f2fs/file.c | 2 +-
fs/f2fs/node.c | 4 +-
fs/fuse/fuse_i.h | 2 +-
fs/iomap/buffered-io.c | 9 +-
fs/nfs/file.c | 2 +-
fs/ntfs/aops.c | 2 +-
fs/verity/verify.c | 4 +-
include/linux/fs.h | 31 +----
include/linux/fsverity.h | 2 +-
include/linux/net.h | 19 +++
include/linux/pagemap.h | 2 -
mm/filemap.c | 12 +-
mm/readahead.c | 204 +++++++++------------------------
28 files changed, 113 insertions(+), 236 deletions(-)
next reply other threads:[~2022-04-01 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 18:54 Matthew Wilcox [this message]
2022-04-01 21:45 ` pr-tracker-bot
2022-04-05 12:08 ` David Sterba
2022-04-05 14:22 ` Matthew Wilcox
2022-04-05 18:09 ` David Sterba
2022-04-06 5:55 ` Christoph Hellwig
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=YkdKgzil38iyc7rX@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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