diff options
| author | Yuezhang Mo <[email protected]> | 2022-04-04 02:58:06 +0000 |
|---|---|---|
| committer | Namjae Jeon <[email protected]> | 2022-05-23 02:17:29 +0000 |
| commit | d8dad2588addd1d861ce19e7df3b702330f0c7e3 (patch) | |
| tree | 959e0e1475aeb1f137861b3a152278fa0d4fea46 /fs/jbd2/commit.c | |
| parent | Linux 5.18 (diff) | |
| download | kernel-d8dad2588addd1d861ce19e7df3b702330f0c7e3.tar.gz kernel-d8dad2588addd1d861ce19e7df3b702330f0c7e3.zip | |
exfat: fix referencing wrong parent directory information after renaming
During renaming, the parent directory information maybe
updated. But the file/directory still references to the
old parent directory information.
This bug will cause 2 problems.
(1) The renamed file can not be written.
[10768.175172] exFAT-fs (sda1): error, failed to bmap (inode : 7afd50e4 iblock : 0, err : -5)
[10768.184285] exFAT-fs (sda1): Filesystem has been set read-only
ash: write error: Input/output error
(2) Some dentries of the renamed file/directory are not set
to deleted after removing the file/directory.
exfat_update_parent_info() is a workaround for the wrong parent
directory information being used after renaming. Now that bug is
fixed, this is no longer needed, so remove it.
Fixes: 5f2aa075070c ("exfat: add inode operations")
Cc: [email protected] # v5.7+
Signed-off-by: Yuezhang Mo <[email protected]>
Reviewed-by: Andy Wu <[email protected]>
Reviewed-by: Aoyama Wataru <[email protected]>
Reviewed-by: Daniel Palmer <[email protected]>
Reviewed-by: Sungjong Seo <[email protected]>
Signed-off-by: Namjae Jeon <[email protected]>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions