All of lore.kernel.org
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 00/12] btrfs: log tree fixes and cleanups
Date: Tue, 24 Jun 2025 15:42:10 +0100	[thread overview]
Message-ID: <cover.1750709410.git.fdmanana@suse.com> (raw)

From: Filipe Manana <fdmanana@suse.com>

Several bug fixes for logging and log replay, plus some cleanups.
Details in the changelogs.

Filipe Manana (12):
  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
  btrfs: use inode already stored in local variable at btrfs_rmdir()
  btrfs: use btrfs inodes in btrfs_rmdir() to avoid so much usage of BTRFS_I()
  btrfs: split inode ref processing from __add_inode_ref() into a helper
  btrfs: split inode rextef processing from __add_inode_ref() into a helper
  btrfs: add btrfs prefix to is_fsstree() and make it return bool
  btrfs: split btrfs_is_fsstree() into multiple if statements for readability

 fs/btrfs/ctree.h        |  17 +-
 fs/btrfs/delayed-ref.c  |  10 +-
 fs/btrfs/disk-io.c      |   8 +-
 fs/btrfs/extent-tree.c  |   6 +-
 fs/btrfs/extent_map.c   |   6 +-
 fs/btrfs/inode.c        |  64 +++----
 fs/btrfs/ioctl.c        |   8 +-
 fs/btrfs/qgroup.c       |  25 +--
 fs/btrfs/relocation.c   |   2 +-
 fs/btrfs/tree-checker.c |  12 +-
 fs/btrfs/tree-log.c     | 362 ++++++++++++++++++++++------------------
 11 files changed, 281 insertions(+), 239 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-06-24 14:42 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 14:42 fdmanana [this message]
2025-06-24 14:42 ` [PATCH 01/12] btrfs: fix missing error handling when searching for inode refs during log replay fdmanana
2025-06-25  9:45   ` Johannes Thumshirn
2025-06-25 10:58     ` Filipe Manana
2025-06-24 14:42 ` [PATCH 02/12] btrfs: fix iteration of extrefs " fdmanana
2025-06-25 10:30   ` Johannes Thumshirn
2025-06-27 10:51   ` Qu Wenruo
2025-06-27 12:09     ` Filipe Manana
2025-06-24 14:42 ` [PATCH 03/12] btrfs: fix inode lookup error handling " fdmanana
2025-06-25 10:34   ` Johannes Thumshirn
2025-06-24 14:42 ` [PATCH 04/12] btrfs: record new subvolume in parent dir earlier to avoid dir logging races fdmanana
2025-06-25 10:39   ` Johannes Thumshirn
2025-06-24 14:42 ` [PATCH 05/12] btrfs: propagate last_unlink_trans earlier when doing a rmdir fdmanana
2025-06-25 10:46   ` Johannes Thumshirn
2025-06-24 14:42 ` [PATCH 06/12] btrfs: use btrfs_record_snapshot_destroy() during rmdir fdmanana
2025-06-25 10:47   ` Johannes Thumshirn
2025-06-25 10:55     ` Filipe Manana
2025-06-27 10:11       ` Johannes Thumshirn
2025-06-24 14:42 ` [PATCH 07/12] btrfs: use inode already stored in local variable at btrfs_rmdir() fdmanana
2025-06-25 10:52   ` Johannes Thumshirn
2025-06-25 10:54     ` Filipe Manana
2025-06-27 10:10   ` Johannes Thumshirn
2025-06-24 14:42 ` [PATCH 08/12] btrfs: use btrfs inodes in btrfs_rmdir() to avoid so much usage of BTRFS_I() fdmanana
2025-06-25 10:54   ` Johannes Thumshirn
2025-06-24 14:42 ` [PATCH 09/12] btrfs: split inode ref processing from __add_inode_ref() into a helper fdmanana
2025-06-25 11:07   ` Johannes Thumshirn
2025-06-24 14:42 ` [PATCH 10/12] btrfs: split inode rextef " fdmanana
2025-06-25 11:35   ` Johannes Thumshirn
2025-06-27 10:09     ` David Sterba
2025-06-24 14:42 ` [PATCH 11/12] btrfs: add btrfs prefix to is_fsstree() and make it return bool fdmanana
2025-06-25 11:35   ` Johannes Thumshirn
2025-06-24 14:42 ` [PATCH 12/12] btrfs: split btrfs_is_fsstree() into multiple if statements for readability fdmanana
2025-06-25 11:37   ` Johannes Thumshirn
2025-06-27 11:04 ` [PATCH 00/12] btrfs: log tree fixes and cleanups Qu Wenruo

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.1750709410.git.fdmanana@suse.com \
    --to=fdmanana@kernel.org \
    --cc=linux-btrfs@vger.kernel.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.