diff options
| author | Jan Kara <jack@suse.cz> | 2019-05-23 23:35:28 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-05-31 06:46:00 -0700 |
| commit | 71e430fd593b2627baaa67e808ff27131b1418e0 (patch) | |
| tree | 16cfc5d6b9e5fe1b2572accb969c8905e0cee5df /fs/ext4/balloc.c | |
| parent | 1d84eb87efceb7bfbe52d7f3539af6c2e9c86870 (diff) | |
| download | linux-stable-71e430fd593b2627baaa67e808ff27131b1418e0.tar.gz linux-stable-71e430fd593b2627baaa67e808ff27131b1418e0.tar.bz2 linux-stable-71e430fd593b2627baaa67e808ff27131b1418e0.zip | |
ext4: do not delete unlinked inode from orphan list on failed truncate
commit ee0ed02ca93ef1ecf8963ad96638795d55af2c14 upstream.
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
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/ext4/balloc.c')
0 files changed, 0 insertions, 0 deletions