]> www.infradead.org Git - users/hch/configfs.git/commit
ext4: handle ext4_mark_inode_dirty errors
authorHarshad Shirwadkar <harshadshirwadkar@gmail.com>
Mon, 27 Apr 2020 01:34:37 +0000 (18:34 -0700)
committerTheodore Ts'o <tytso@mit.edu>
Thu, 4 Jun 2020 03:16:50 +0000 (23:16 -0400)
commit4209ae12b12265d475bba28634184423149bd14f
treed1f29a46922752c0c5d5b68ec93fa8c11943e653
parent8418897f1bf87da0cb6936489d57a4320c32c0af
ext4: handle ext4_mark_inode_dirty errors

ext4_mark_inode_dirty() can fail for real reasons. Ignoring its return
value may lead ext4 to ignore real failures that would result in
corruption / crashes. Harden ext4_mark_inode_dirty error paths to fail
as soon as possible and return errors to the caller whenever
appropriate.

One of the possible scnearios when this bug could affected is that
while creating a new inode, its directory entry gets added
successfully but while writing the inode itself mark_inode_dirty
returns error which is ignored. This would result in inconsistency
that the directory entry points to a non-existent inode.

Ran gce-xfstests smoke tests and verified that there were no
regressions.

Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Link: https://lore.kernel.org/r/20200427013438.219117-1-harshadshirwadkar@gmail.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
12 files changed:
fs/ext4/acl.c
fs/ext4/ext4.h
fs/ext4/ext4_jbd2.h
fs/ext4/extents.c
fs/ext4/file.c
fs/ext4/indirect.c
fs/ext4/inline.c
fs/ext4/inode.c
fs/ext4/migrate.c
fs/ext4/namei.c
fs/ext4/super.c
fs/ext4/xattr.c