[GIT PULL] Btrfs fixes for 5.11-rc5

* [GIT PULL] Btrfs fixes for 5.11-rc5
@ 2021-01-20 21:49 David Sterba
  2021-01-20 22:26 ` pr-tracker-bot
  0 siblings, 1 reply; 2+ messages in thread
From: David Sterba @ 2021-01-20 21:49 UTC (permalink / raw)
  To: torvalds; +Cc: David Sterba, linux-btrfs, linux-kernel

Hi,

a few more one line fixes for various bugs, stable material.

- fix send when emitting clone operation from the same file and root

- fix double free on error when cleaning backrefs

- lockdep fix during relocation

- handle potential error during reloc when starting transaction

- skip running delayed refs during commit (leftover from code removal in
  this dev cycle)

Please pull thanks.

----------------------------------------------------------------
The following changes since commit e076ab2a2ca70a0270232067cd49f76cd92efe64:

  btrfs: shrink delalloc pages instead of full inodes (2021-01-08 16:36:44 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.11-rc4-tag

for you to fetch changes up to 34d1eb0e599875064955a74712f08ff14c8e3d5f:

  btrfs: don't clear ret in btrfs_start_dirty_block_groups (2021-01-18 16:00:11 +0100)

----------------------------------------------------------------
David Sterba (1):
      btrfs: no need to run delayed refs after commit_fs_roots during commit

Filipe Manana (1):
      btrfs: send: fix invalid clone operations when cloning from the same file and root

Josef Bacik (4):
      btrfs: don't get an EINTR during drop_snapshot for reloc
      btrfs: do not double free backref nodes on error
      btrfs: fix lockdep splat in btrfs_recover_relocation
      btrfs: don't clear ret in btrfs_start_dirty_block_groups

 fs/btrfs/backref.c     |  2 +-
 fs/btrfs/block-group.c |  3 ++-
 fs/btrfs/extent-tree.c | 10 +++++++++-
 fs/btrfs/send.c        | 15 +++++++++++++++
 fs/btrfs/transaction.c |  8 --------
 fs/btrfs/volumes.c     |  2 ++
 6 files changed, 29 insertions(+), 11 deletions(-)

^ permalink raw reply	[flat|nested] 2+ messages in thread