summaryrefslogtreecommitdiffstats
path: root/Documentation/atomic_t.txt
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2019-05-24 05:35:28 +0200
committerTheodore Ts'o <tytso@mit.edu>2019-05-24 05:35:28 +0200
commitee0ed02ca93ef1ecf8963ad96638795d55af2c14 (patch)
treed466f5a61e165caf2a4a70b27234d448a361664d /Documentation/atomic_t.txt
parentext4: wait for outstanding dio during truncate in nojournal mode (diff)
downloadlinux-ee0ed02ca93ef1ecf8963ad96638795d55af2c14.tar.xz
linux-ee0ed02ca93ef1ecf8963ad96638795d55af2c14.zip
ext4: do not delete unlinked inode from orphan list on failed truncate
It is possible that unlinked inode enters ext4_setattr() (e.g. if somebody calls ftruncate(2) on unlinked but still open file). In such case we should not delete the inode from the orphan list if truncate fails. Note that this is mostly a theoretical concern as filesystem is corrupted if we reach this path anyway but let's be consistent in our orphan handling. Reviewed-by: Ira Weiny <ira.weiny@intel.com> Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Cc: stable@kernel.org
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions