Linux Btrfs filesystem development
 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.17-rc3
Date: Mon, 18 Aug 2025 18:14:28 +0200	[thread overview]
Message-ID: <cover.1755532653.git.dsterba@suse.com> (raw)

Hi,

please pull the following branch. There are several zoned mode fixes,
mount option printing fixups, folio state handling fixes and one log
replay fix. Thanks.

- zoned mode
  - zone activation and finish fixes
  - block group reservation fixes

- mount option fixes
  - bring back printing of mount options with key=value that got
    accidentally dropped during mount option parsing in 6.8
  - fix inverse logic or typos when printing nodatasum/nodatacow

- folio status fixes
  - writeback fixes in zoned mode
  - properly reset dirty/writeback if submission fails
  - properly handle TOWRITE xarray mark/tag

- do not set mtime/ctime to current time when unlinking for log replay

----------------------------------------------------------------
The following changes since commit 7b632596188e1973c6b3ac1c9f8252f735e1039f:

  btrfs: fix iteration bug in __qgroup_excl_accounting() (2025-08-07 17:07:16 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.17-rc2-tag

for you to fetch changes up to 74857fdc5dd2cdcdeb6e99bdf26976fd9299d2bb:

  btrfs: fix printing of mount info messages for NODATACOW/NODATASUM (2025-08-13 14:08:58 +0200)

----------------------------------------------------------------
Filipe Manana (1):
      btrfs: do not set mtime/ctime to current time when unlinking for log replay

Johannes Thumshirn (1):
      btrfs: zoned: skip ZONE FINISH of conventional zones

Kyoji Ogasawara (3):
      btrfs: fix incorrect log message for nobarrier mount option
      btrfs: restore mount option info messages during mount
      btrfs: fix printing of mount info messages for NODATACOW/NODATASUM

Naohiro Aota (5):
      btrfs: zoned: fix data relocation block group reservation
      btrfs: zoned: fix write time activation failure for metadata block group
      btrfs: zoned: limit active zones to max_open_zones
      btrfs: subpage: keep TOWRITE tag until folio is cleaned
      btrfs: fix buffer index in wait_eb_writebacks()

Qu Wenruo (3):
      btrfs: clear block dirty if submit_one_sector() failed
      btrfs: clear block dirty if btrfs_writepage_cow_fixup() failed
      btrfs: clear TAG_TOWRITE from buffer tree when submitting a tree block

 fs/btrfs/extent_io.c |  24 ++++++++--
 fs/btrfs/inode.c     |  29 +++++++----
 fs/btrfs/subpage.c   |  19 +++++++-
 fs/btrfs/super.c     |  13 +++--
 fs/btrfs/zoned.c     | 133 ++++++++++++++++++++++++++++++++++++++-------------
 5 files changed, 163 insertions(+), 55 deletions(-)

             reply	other threads:[~2025-08-18 16:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 16:14 David Sterba [this message]
2025-08-18 16:40 ` [GIT PULL] Btrfs fixes for 6.17-rc3 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.1755532653.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