diff options
| author | Jan Kara <[email protected]> | 2019-05-23 23:35:28 -0400 |
|---|---|---|
| committer | Theodore Ts'o <[email protected]> | 2019-05-23 23:35:28 -0400 |
| commit | ee0ed02ca93ef1ecf8963ad96638795d55af2c14 (patch) | |
| tree | d466f5a61e165caf2a4a70b27234d448a361664d /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 82a25b027ca48d7ef197295846b352345853dfa8 (diff) | |
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 <[email protected]>
Signed-off-by: Jan Kara <[email protected]>
Signed-off-by: Theodore Ts'o <[email protected]>
Cc: [email protected]
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions