From: Jan Kara <email@example.com> To: <firstname.lastname@example.org> Cc: Christoph Hellwig <email@example.com>, Dave Chinner <firstname.lastname@example.org>, email@example.com, Chao Yu <firstname.lastname@example.org>, Damien Le Moal <email@example.com>, "Darrick J. Wong" <firstname.lastname@example.org>, Jaegeuk Kim <email@example.com>, Jeff Layton <firstname.lastname@example.org>, Johannes Thumshirn <email@example.com>, firstname.lastname@example.org, <email@example.com>, firstname.lastname@example.org, <email@example.com>, <firstname.lastname@example.org>, Miklos Szeredi <email@example.com>, Steve French <firstname.lastname@example.org>, Ted Tso <email@example.com>, Matthew Wilcox <firstname.lastname@example.org>, Jan Kara <email@example.com> Subject: [PATCH 0/14 v7] fs: Hole punch vs page cache filling races Date: Mon, 7 Jun 2021 16:52:10 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) Hello, here is another version of my patches to address races between hole punching and page cache filling functions for ext4 and other filesystems. The biggest change since the last time is providing function to lock two mappings and using it from XFS. Other changes were pretty minor. Out of all filesystem supporting hole punching, only GFS2 and OCFS2 remain unresolved. GFS2 people are working on their own solution (cluster locking is involved), OCFS2 has even bigger issues (maintainers informed, looking into it). As a next step, I'd like to actually make sure all calls to truncate_inode_pages() happen under mapping->invalidate_lock, add the assert and then we can also get rid of i_size checks in some places (truncate can use the same serialization scheme as hole punch). But that step is mostly a cleanup so I'd like to get these functional fixes in first. Note that the first patch of the series is already in mm tree but I'm submitting it here so that the series applies to Linus' tree cleanly. Changes since v6: * Added some reviewed-by tags * Added wrapper for taking invalidate_lock similar to inode_lock * Renamed wrappers for taking invalidate_lock for two inodes * Added xfs patch to make xfs_isilocked() work better even without lockdep * Some minor documentation fixes Changes since v5: * Added some reviewed-by tags * Added functions for locking two mappings and using them from XFS where needed * Some minor code style & comment fixes Changes since v4: * Rebased onto 5.13-rc1 * Removed shmfs conversion patches * Fixed up zonefs changelog * Fixed up XFS comments * Added patch fixing up definition of file_operations in Documentation/vfs/ * Updated documentation and comments to explain invalidate_lock is used also to prevent changes through memory mappings to existing pages for some VFS operations. Changes since v3: * Renamed and moved lock to struct address_space * Added conversions of tmpfs, ceph, cifs, fuse, f2fs * Fixed error handling path in filemap_read() * Removed .page_mkwrite() cleanup from the series for now Changes since v2: * Added documentation and comments regarding lock ordering and how the lock is supposed to be used * Added conversions of ext2, xfs, zonefs * Added patch removing i_mapping_sem protection from .page_mkwrite handlers Changes since v1: * Moved to using inode->i_mapping_sem instead of aops handler to acquire appropriate lock --- Motivation: Amir has reported  a that ext4 has a potential issues when reads can race with hole punching possibly exposing stale data from freed blocks or even corrupting filesystem when stale mapping data gets used for writeout. The problem is that during hole punching, new page cache pages can get instantiated and block mapping from the looked up in a punched range after truncate_inode_pages() has run but before the filesystem removes blocks from the file. In principle any filesystem implementing hole punching thus needs to implement a mechanism to block instantiating page cache pages during hole punching to avoid this race. This is further complicated by the fact that there are multiple places that can instantiate pages in page cache. We can have regular read(2) or page fault doing this but fadvise(2) or madvise(2) can also result in reading in page cache pages through force_page_cache_readahead(). There are couple of ways how to fix this. First way (currently implemented by XFS) is to protect read(2) and *advise(2) calls with i_rwsem so that they are serialized with hole punching. This is easy to do but as a result all reads would then be serialized with writes and thus mixed read-write workloads suffer heavily on ext4. Thus this series introduces inode->i_mapping_sem and uses it when creating new pages in the page cache and looking up their corresponding block mapping. We also replace EXT4_I(inode)->i_mmap_sem with this new rwsem which provides necessary serialization with hole punching for ext4. Honza  https://lore.kernel.org/linux-fsdevel/CAOQ4uxjQNmxqmtA_VbYW0Su9rKRk2zobJmahcyeaEVOFKVQ5dw@mail.gmail.com/ Previous versions: Link: https://email@example.com/ Link: https://firstname.lastname@example.org Link: https://email@example.com Link: https://firstname.lastname@example.org Link: http://email@example.com
next reply other threads:[~2021-06-07 14:52 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-07 14:52 Jan Kara [this message] 2021-06-07 14:52 ` [PATCH 01/14] mm: Fix comments mentioning i_mutex Jan Kara 2021-06-07 15:31 ` Darrick J. Wong 2021-06-10 9:06 ` Ming Lei 2021-06-10 10:40 ` Jan Kara 2021-06-07 14:52 ` [PATCH 02/14] documentation: Sync file_operations members with reality Jan Kara 2021-06-07 14:52 ` [PATCH 03/14] mm: Protect operations adding pages to page cache with invalidate_lock Jan Kara 2021-06-07 16:09 ` Darrick J. Wong 2021-06-08 12:19 ` Jan Kara 2021-06-07 14:52 ` [PATCH 04/14] mm: Add functions to lock invalidate_lock for two mappings Jan Kara 2021-06-07 15:46 ` Darrick J. Wong 2021-06-07 14:52 ` [PATCH 05/14] ext4: Convert to use mapping->invalidate_lock Jan Kara 2021-06-07 14:52 ` [PATCH 06/14] ext2: Convert to using invalidate_lock Jan Kara 2021-06-07 14:52 ` [PATCH 07/14] xfs: Refactor xfs_isilocked() Jan Kara 2021-06-07 15:49 ` Darrick J. Wong 2021-06-08 22:18 ` Dave Chinner 2021-06-07 14:52 ` [PATCH 08/14] xfs: Convert to use invalidate_lock Jan Kara 2021-06-07 15:56 ` Darrick J. Wong 2021-06-08 12:23 ` Jan Kara 2021-06-07 14:52 ` [PATCH 09/14] xfs: Convert double locking of MMAPLOCK to use VFS helpers Jan Kara 2021-06-07 15:57 ` Darrick J. Wong 2021-06-07 14:52 ` [PATCH 10/14] zonefs: Convert to using invalidate_lock Jan Kara 2021-06-07 14:52 ` [PATCH 11/14] f2fs: " Jan Kara 2021-06-07 14:52 ` [PATCH 12/14] fuse: " Jan Kara 2021-06-10 12:42 ` Miklos Szeredi 2021-06-07 14:52 ` [PATCH 13/14] ceph: Fix race between hole punch and page fault Jan Kara 2021-06-07 14:52 ` [PATCH 14/14] cifs: " Jan Kara 2021-06-08 11:54 ` [PATCH 0/14 v7] fs: Hole punch vs page cache filling races 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/14 v7] fs: Hole punch vs page cache filling races' \ /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
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).