• Chris Mason's avatar
    Btrfs: Make sure i_nlink doesn't hit zero too soon during log replay · a74ac322
    Chris Mason authored
    
    
    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: default avatarChris Mason <chris.mason@oracle.com>
    a74ac322