diff options
| author | Jaegeuk Kim <jaegeuk.kim@samsung.com> | 2013-05-28 09:19:22 +0900 |
|---|---|---|
| committer | Chanho Park <chanho61.park@samsung.com> | 2014-11-18 11:43:49 +0900 |
| commit | cd30815328214eada9b1d2db98d4f083db1c484d (patch) | |
| tree | 1c71e05788e9283f3ca5ad32262cd810e0aca0c6 /drivers | |
| parent | d459aab1f3a0b7b91a3450769b1d85611acdefc5 (diff) | |
| download | linux-3.10-cd30815328214eada9b1d2db98d4f083db1c484d.tar.gz linux-3.10-cd30815328214eada9b1d2db98d4f083db1c484d.tar.bz2 linux-3.10-cd30815328214eada9b1d2db98d4f083db1c484d.zip | |
f2fs: fix dentry recovery routine
The error scenario is:
1. create /a
(1.a link /a /b)
2. sync
3. unlinke /a
4. create /a
5. fsync /a
6. Sudden power-off
When the f2fs recovers the fsynced dentry, /a, we discover an exsiting dentry at
f2fs_find_entry() in recover_dentry().
In such the case, we should unlink the existing dentry and its inode
and then recover newly created dentry.
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions