| commit | a74ac3220774d33db967088906dc3351829e2d3a | |
| author | Chris Mason <chris.mason@oracle.com> | |
| Tue, 24 Mar 2009 14:24:13 +0000 (24 10:24 -0400) | ||
| committer | Chris Mason <chris.mason@oracle.com> | |
| Tue, 24 Mar 2009 20:14:51 +0000 (24 16:14 -0400) | ||
| tree | 292fe0b88a5917d3b282b6a1cdfca170f9405132 | treesnapshot (tar.gz zip) |
| parent | a4b6e07d1a8a9b907e82b9acbf51a026fbb9301c | commitdiff |
Btrfs: Make sure i_nlink doesn't hit zero too soon during log replay
During log replay, inodes are copied from the log to the main filesystem
btrees. Sometimes they have a zero link count in the log but they actually
gain links during the replay or have some in the main btree.
This patch updates the link count to be at least one after copying the
inode out of the log. This makes sure the inode is deleted during an
iput while the rest of the replay code is still working on it.
The log replay has fixup code to make sure that link counts are correct
at the end of the replay, so we could use any non-zero number here and
it would work fine.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
During log replay, inodes are copied from the log to the main filesystem
btrees. Sometimes they have a zero link count in the log but they actually
gain links during the replay or have some in the main btree.
This patch updates the link count to be at least one after copying the
inode out of the log. This makes sure the inode is deleted during an
iput while the rest of the replay code is still working on it.
The log replay has fixup code to make sure that link counts are correct
at the end of the replay, so we could use any non-zero number here and
it would work fine.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
| fs/btrfs/tree-log.c | diffblobblamehistory |