mirror of https://lore.kernel.org/lkml/
 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.16-rc5
Date: Thu,  3 Jul 2025 21:29:28 +0200	[thread overview]
Message-ID: <cover.1751564436.git.dsterba@suse.com> (raw)

Hi,

please pull a few more fixes. There are mostly tree-log fixes and a free
space tree rebuild fix.

Thanks.

- tree-log fixes
  - fixes of log tracking of directories and subvolumes
  - fix iteration and error handling of inode references during log
    replay

- fix free space tree rebuild (reported by syzbot)

----------------------------------------------------------------
The following changes since commit c0d90a79e8e65b89037508276b2b31f41a1b3783:

  btrfs: zoned: fix alloc_offset calculation for partly conventional block groups (2025-06-19 15:21:15 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.16-rc4-tag

for you to fetch changes up to 157501b0469969fc1ba53add5049575aadd79d80:

  btrfs: use btrfs_record_snapshot_destroy() during rmdir (2025-06-27 19:58:12 +0200)

----------------------------------------------------------------
Filipe Manana (7):
      btrfs: fix failure to rebuild free space tree using multiple transactions
      btrfs: fix missing error handling when searching for inode refs during log replay
      btrfs: fix iteration of extrefs during log replay
      btrfs: fix inode lookup error handling during log replay
      btrfs: record new subvolume in parent dir earlier to avoid dir logging races
      btrfs: propagate last_unlink_trans earlier when doing a rmdir
      btrfs: use btrfs_record_snapshot_destroy() during rmdir

 fs/btrfs/block-group.h     |   2 +
 fs/btrfs/free-space-tree.c |  40 +++++++++++++
 fs/btrfs/inode.c           |  36 ++++++------
 fs/btrfs/ioctl.c           |   4 +-
 fs/btrfs/tree-log.c        | 137 +++++++++++++++++++++++----------------------
 5 files changed, 131 insertions(+), 88 deletions(-)

             reply	other threads:[~2025-07-03 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 19:29 David Sterba [this message]
2025-07-03 22:12 ` 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.1751564436.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

all inboxes | Powered by JetHome®