All of lore.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.14-rc2
Date: Mon, 12 Jul 2021 21:28:00 +0200	[thread overview]
Message-ID: <cover.1626115408.git.dsterba@suse.com> (raw)

Hi,

please pull the following fixes, all are for the zoned mode support.
Thanks.

- fix deadlock when allocating system chunk

- fix wrong mutex unlock on an error path

- fix extent map splitting for append operation

- update and fix message reporting unusable chunk space

- don't block when background zone reclaim runs with balance in parallel

----------------------------------------------------------------
The following changes since commit 629e33a16809ae0274e1f5fc3d22b92b9bd0fdf1:

  btrfs: remove unused btrfs_fs_info::total_pinned (2021-06-22 19:58:26 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.14-rc1-tag

for you to fetch changes up to ea32af47f00a046a1f953370514d6d946efe0152:

  btrfs: zoned: fix wrong mutex unlock on failure to allocate log root tree (2021-07-07 18:27:44 +0200)

----------------------------------------------------------------
David Sterba (1):
      btrfs: zoned: fix types for u64 division in btrfs_reclaim_bgs_work

Filipe Manana (3):
      btrfs: fix deadlock with concurrent chunk allocations involving system chunks
      btrfs: rework chunk allocation to avoid exhaustion of the system chunk array
      btrfs: zoned: fix wrong mutex unlock on failure to allocate log root tree

Johannes Thumshirn (2):
      btrfs: zoned: print unusable percentage when reclaiming block groups
      btrfs: don't block if we can't acquire the reclaim lock

Naohiro Aota (1):
      btrfs: properly split extent_map for REQ_OP_ZONE_APPEND

 fs/btrfs/block-group.c | 367 ++++++++++++++++++++++++++++++++++++-------------
 fs/btrfs/block-group.h |   6 +-
 fs/btrfs/ctree.c       |  67 ++-------
 fs/btrfs/inode.c       | 147 ++++++++++++++++----
 fs/btrfs/transaction.c |  15 +-
 fs/btrfs/transaction.h |   9 +-
 fs/btrfs/tree-log.c    |   2 +-
 fs/btrfs/volumes.c     | 355 +++++++++++++++++++++++++++++++++++------------
 fs/btrfs/volumes.h     |   5 +-
 9 files changed, 687 insertions(+), 286 deletions(-)

             reply	other threads:[~2021-07-12 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12 19:28 David Sterba [this message]
2021-07-13 19:17 ` [GIT PULL] Btrfs fixes for 5.14-rc2 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.1626115408.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.