ext2: Fix data integrity writeout issues

Browse source

Ext2 could fail to properly write out inode on fsync(2) due to races
with WB_SYNC_NONE writeback. Several racing fsyncs could also result in
some fsync returning earlier than all metadata buffers were properly
persisted. Finally DIRSYNC handling was not properly persisting all
inode related metadata.

Fix all these issues by using new .sync_inode_metadata method which
makes sure all inode related metadata is written to disk during any
WB_SYNC_ALL writeback.

Signed-off-by: Jan Kara <jack@suse.cz>
Link: https://patch.msgid.link/20260727104923.3828017-29-jack@suse.cz
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>

...

This commit is contained in:

Jan Kara 2026-07-27 12:49:27 +02:00 • committed by Christian Brauner

parent 74d4faaa76

commit 917e583992

No known key found for this signature in database

GPG key ID: 91C61BC06578DCA2

5 changed files with 34 additions and 37 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

fs/ext2/dir.c

View file

3

fs/ext2/ext2.h

View file

17

fs/ext2/file.c

View file

48

fs/ext2/inode.c

View file

1

fs/ext2/super.c

View file