public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.11-rc5
Date: Wed, 20 Jan 2021 22:49:46 +0100	[thread overview]
Message-ID: <cover.1611178630.git.dsterba@suse.com> (raw)

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(-)

             reply	other threads:[~2021-01-20 22:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 21:49 David Sterba [this message]
2021-01-20 22:26 ` [GIT PULL] Btrfs fixes for 5.11-rc5 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1611178630.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox