diff options
| author | Jan Kara <jack@suse.cz> | 2019-05-24 06:35:28 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-05-31 16:47:10 +0300 |
| commit | db30e95da574aed2f7a9b3defa68d01e6fe02bd6 (patch) | |
| tree | 4f6e2583b9a7e2d944ca37f4aaf32c1c86fd55b8 /fs | |
| parent | f77efdaa77b777e9b983696fa5a4a29a2768d6dd (diff) | |
| download | linux-db30e95da574aed2f7a9b3defa68d01e6fe02bd6.tar.xz | |
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')
| -rw-r--r-- | fs/ext4/inode.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c index d3ef946df585..862766a1b080 100644 --- a/fs/ext4/inode.c +++ b/fs/ext4/inode.c @@ -5450,7 +5450,7 @@ int ext4_setattr(struct dentry *dentry, struct iattr *attr) up_write(&EXT4_I(inode)->i_data_sem); ext4_journal_stop(handle); if (error) { - if (orphan) + if (orphan && inode->i_nlink) ext4_orphan_del(NULL, inode); goto err_out; } |