From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, "Darrick J. Wong" <djwong@kernel.org>
Subject: [GIT PULL] Hole puch vs page cache filling races fixes for 5.14-rc1
Date: Wed, 30 Jun 2021 19:25:29 +0200 [thread overview]
Message-ID: <20210630172529.GB13951@quack2.suse.cz> (raw)
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git hole_punch_for_v5.14-rc1
to get patches that fix races leading to possible data corruption or stale
data exposure in multiple filesystems when hole punching races with
operations such as readahead.
Top of the tree is e996ae6bdbd1. The full shortlog is:
Jan Kara (13):
mm: Fix comments mentioning i_mutex
documentation: Sync file_operations members with reality
mm: Protect operations adding pages to page cache with invalidate_lock
mm: Add functions to lock invalidate_lock for two mappings
ext4: Convert to use mapping->invalidate_lock
ext2: Convert to using invalidate_lock
xfs: Convert to use invalidate_lock
xfs: Convert double locking of MMAPLOCK to use VFS helpers
zonefs: Convert to using invalidate_lock
f2fs: Convert to using invalidate_lock
fuse: Convert to using invalidate_lock
ceph: Fix race between hole punch and page fault
cifs: Fix race between hole punch and page fault
Pavel Reichl (1):
xfs: Refactor xfs_isilocked()
The diffstat is
Documentation/filesystems/locking.rst | 77 +++++++++++++++-------
fs/ceph/addr.c | 9 ++-
fs/ceph/file.c | 2 +
fs/cifs/smb2ops.c | 2 +
fs/ext2/ext2.h | 11 ----
fs/ext2/file.c | 7 +-
fs/ext2/inode.c | 12 ++--
fs/ext2/super.c | 3 -
fs/ext4/ext4.h | 10 ---
fs/ext4/extents.c | 25 +++----
fs/ext4/file.c | 13 ++--
fs/ext4/inode.c | 47 +++++--------
fs/ext4/ioctl.c | 4 +-
fs/ext4/super.c | 13 ++--
fs/ext4/truncate.h | 8 ++-
fs/f2fs/data.c | 4 +-
fs/f2fs/f2fs.h | 1 -
fs/f2fs/file.c | 62 +++++++++--------
fs/f2fs/super.c | 1 -
fs/fuse/dax.c | 50 +++++++-------
fs/fuse/dir.c | 11 ++--
fs/fuse/file.c | 10 +--
fs/fuse/fuse_i.h | 7 --
fs/fuse/inode.c | 1 -
fs/inode.c | 2 +
fs/xfs/xfs_bmap_util.c | 15 +++--
fs/xfs/xfs_file.c | 13 ++--
fs/xfs/xfs_inode.c | 121 ++++++++++++++++++----------------
fs/xfs/xfs_inode.h | 3 +-
fs/xfs/xfs_super.c | 2 -
fs/zonefs/super.c | 23 ++-----
fs/zonefs/zonefs.h | 7 +-
include/linux/fs.h | 39 +++++++++++
mm/filemap.c | 113 ++++++++++++++++++++++++++-----
mm/madvise.c | 2 +-
mm/memory-failure.c | 2 +-
mm/readahead.c | 2 +
mm/rmap.c | 41 ++++++------
mm/shmem.c | 20 +++---
mm/truncate.c | 9 +--
40 files changed, 453 insertions(+), 351 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2021-06-30 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 17:25 Jan Kara [this message]
2021-07-01 1:15 ` [GIT PULL] Hole puch vs page cache filling races fixes for 5.14-rc1 Linus Torvalds
2021-07-01 16:19 ` Jan Kara
2021-07-01 18:04 ` Linus Torvalds
2021-07-06 20:17 ` Jan Kara
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=20210630172529.GB13951@quack2.suse.cz \
--to=jack@suse.cz \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).