diff options
| author | OGAWA Hirofumi <[email protected]> | 2024-10-04 15:03:49 +0900 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2024-10-17 00:28:06 -0700 |
| commit | 963a7f4d3b90ee195b895ca06b95757fcba02d1a (patch) | |
| tree | 25cfbf5b825f46ef79ac962e3af40b725287b1e8 | |
| parent | 08cfa12adf888db98879dbd735bc741360a34168 (diff) | |
fat: fix uninitialized variable
syszbot produced this with a corrupted fs image. In theory, however an IO
error would trigger this also.
This affects just an error report, so should not be a serious error.
Link: https://lkml.kernel.org/r/[email protected]
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: OGAWA Hirofumi <[email protected]>
Reported-by: [email protected]
Cc: <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
| -rw-r--r-- | fs/fat/namei_vfat.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/fat/namei_vfat.c b/fs/fat/namei_vfat.c index 6423e1dedf14..15bf32c21ac0 100644 --- a/fs/fat/namei_vfat.c +++ b/fs/fat/namei_vfat.c @@ -1037,7 +1037,7 @@ error_inode: if (corrupt < 0) { fat_fs_error(new_dir->i_sb, "%s: Filesystem corrupted (i_pos %lld)", - __func__, sinfo.i_pos); + __func__, new_i_pos); } goto out; } |