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 6.3-rc4
Date: Fri, 24 Mar 2023 00:31:40 +0100	[thread overview]
Message-ID: <cover.1679610326.git.dsterba@suse.com> (raw)

Hi,

a few more fixes, the zoned accounting fix is spread across a few
patches, preparatory and the actual fixes. Please pull, thanks.

- zoned mode
  - fix accounting of unusable zone space
  - fix zone activation condition for DUP profile
  - preparatory patches

- improved error handling of missing chunks

- fix compiler warning

----------------------------------------------------------------
The following changes since commit 675dfe1223a69e270b3d52cb0211c8a501455cec:

  btrfs: fix block group item corruption after inserting new block group (2023-03-08 01:14:01 +0100)

are available in the Git repository at:

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

for you to fetch changes up to e15acc25880cf048dba9df94d76ed7e7e10040e6:

  btrfs: zoned: drop space_info->active_total_bytes (2023-03-15 20:51:07 +0100)

----------------------------------------------------------------
Josef Bacik (2):
      btrfs: rename BTRFS_FS_NO_OVERCOMMIT to BTRFS_FS_ACTIVE_ZONE_TRACKING
      btrfs: use temporary variable for space_info in btrfs_update_block_group

Naohiro Aota (3):
      btrfs: zoned: fix btrfs_can_activate_zone() to support DUP profile
      btrfs: zoned: count fresh BG region as zone unusable
      btrfs: zoned: drop space_info->active_total_bytes

Qu Wenruo (1):
      btrfs: handle missing chunk mapping more gracefully

Sweet Tea Dorminy (1):
      btrfs: fix compiler warning on SPARC/PA-RISC handling fscrypt_setup_filename

 fs/btrfs/block-group.c      | 28 ++++++++++++----------------
 fs/btrfs/free-space-cache.c |  8 +++++++-
 fs/btrfs/fs.h               |  7 ++-----
 fs/btrfs/inode.c            |  7 ++++++-
 fs/btrfs/space-info.c       | 42 ++++++++++--------------------------------
 fs/btrfs/space-info.h       |  2 --
 fs/btrfs/volumes.c          |  3 ++-
 fs/btrfs/zoned.c            | 45 ++++++++++++++++++++++++++++++++-------------
 8 files changed, 71 insertions(+), 71 deletions(-)

             reply	other threads:[~2023-03-23 23:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 23:31 David Sterba [this message]
2023-03-24 16:31 ` [GIT PULL] Btrfs fixes for 6.3-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.1679610326.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.