diff options
| author | Chris Mason <clm@fb.com> | 2014-12-31 18:18:29 +0100 |
|---|---|---|
| committer | Chris Mason <clm@fb.com> | 2015-01-02 20:47:56 +0100 |
| commit | 6f8960541b1eb6054a642da48daae2320fddba93 (patch) | |
| tree | 00700888057da8537676a6af12ed85675c90df18 /fs/ecryptfs | |
| parent | Btrfs: correctly get tree level in tree_backref_for_extent (diff) | |
| download | linux-6f8960541b1eb6054a642da48daae2320fddba93.tar.xz linux-6f8960541b1eb6054a642da48daae2320fddba93.zip | |
Btrfs: don't delay inode ref updates during log replay
Commit 1d52c78afbb (Btrfs: try not to ENOSPC on log replay) added a
check to skip delayed inode updates during log replay because it
confuses the enospc code. But the delayed processing will end up
ignoring delayed refs from log replay because the inode itself wasn't
put through the delayed code.
This can end up triggering a warning at commit time:
WARNING: CPU: 2 PID: 778 at fs/btrfs/delayed-inode.c:1410 btrfs_assert_delayed_root_empty+0x32/0x34()
Which is repeated for each commit because we never process the delayed
inode ref update.
The fix used here is to change btrfs_delayed_delete_inode_ref to return
an error if we're currently in log replay. The caller will do the ref
deletion immediately and everything will work properly.
Signed-off-by: Chris Mason <clm@fb.com>
cc: stable@vger.kernel.org # v3.18 and any stable series that picked 1d52c78afbbf80b58299e076a159617d6b42fe3c
Diffstat (limited to 'fs/ecryptfs')
0 files changed, 0 insertions, 0 deletions