public inbox for linux-btrfs@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.9-rc4
Date: Tue,  1 Sep 2020 01:20:49 +0200	[thread overview]
Message-ID: <cover.1598905089.git.dsterba@suse.com> (raw)

Hi,

two small fixes and a bunch of lockdep fixes for warnings that show up
with an upcoming tree locking update but are valid with current locks as
well.  Please pull, thanks.

* fix bug in free space bitmap/extent switch logic

* several lockdep warning fixes

* clarify tree-checker error message

----------------------------------------------------------------
The following changes since commit a84d5d429f9eb56f81b388609841ed993f0ddfca:

  btrfs: detect nocow for swap after snapshot delete (2020-08-21 12:21:23 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.9-rc3-tag

for you to fetch changes up to f96d6960abbc52e26ad124e69e6815283d3e1674:

  btrfs: tree-checker: fix the error message for transid error (2020-08-27 14:16:05 +0200)

----------------------------------------------------------------
Josef Bacik (5):
      btrfs: drop path before adding new uuid tree entry
      btrfs: fix potential deadlock in the search ioctl
      btrfs: allocate scrub workqueues outside of locks
      btrfs: set the correct lockdep class for new nodes
      btrfs: set the lockdep class for log tree extent buffers

Marcos Paulo de Souza (1):
      btrfs: block-group: fix free-space bitmap threshold

Qu Wenruo (1):
      btrfs: tree-checker: fix the error message for transid error

 fs/btrfs/block-group.c     |   4 +-
 fs/btrfs/ctree.c           |   6 ++-
 fs/btrfs/extent-tree.c     |   2 +-
 fs/btrfs/extent_io.c       |   8 +--
 fs/btrfs/extent_io.h       |   6 +--
 fs/btrfs/free-space-tree.c |   4 ++
 fs/btrfs/ioctl.c           |  27 +++++++---
 fs/btrfs/scrub.c           | 122 ++++++++++++++++++++++++++-------------------
 fs/btrfs/tree-checker.c    |   2 +-
 fs/btrfs/volumes.c         |   3 +-
 10 files changed, 113 insertions(+), 71 deletions(-)

             reply	other threads:[~2020-08-31 23:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 23:20 David Sterba [this message]
2020-09-02  2:45 ` [GIT PULL] Btrfs fixes for 5.9-rc4 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.1598905089.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