aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2024-05-01 00:20:10 -0400
committerTheodore Ts'o <tytso@mit.edu>2024-05-01 00:20:10 -0400
commit5f3a677bfccfa34c1387336b306ab5805acf95ae (patch)
tree38505ea4cc148e7b1d4791d8e9336e08f3c46f7e
parent7480dcacb0b79faf8c7608ce136c37d6cc6e2254 (diff)
downloade2fsprogs-5f3a677bfccfa34c1387336b306ab5805acf95ae.tar.gz
resize2fs: mark that the error return is deliberately ignored
When moving the inode table, if writing the (partially overlapping) inode table fails, we need to write it back in its original location before bailing out. If that write unding the initial write fails, there's nothing we can do, so we ignore it. Mark this to avoid a false positive from Coverity. Fixes-Coverity-bug: 1432422 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
-rw-r--r--resize/resize2fs.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/resize/resize2fs.c b/resize/resize2fs.c
index f4a409805..e590f9341 100644
--- a/resize/resize2fs.c
+++ b/resize/resize2fs.c
@@ -2595,8 +2595,8 @@ static errcode_t move_itables(ext2_resize_t rfs)
retval = io_channel_write_blk64(fs->io, new_blk,
num, rfs->itable_buf);
if (retval) {
- io_channel_write_blk64(fs->io, old_blk,
- num, rfs->itable_buf);
+ (void) io_channel_write_blk64(fs->io, old_blk,
+ num, rfs->itable_buf);
goto errout;
}
if (n > diff) {