From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/7] btrfs: minor tweaks and cleanups to the super block writing path
Date: Wed, 4 Feb 2026 15:51:57 +0000 [thread overview]
Message-ID: <cover.1770212626.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Details in the change logs.
Filipe Manana (7):
btrfs: change unaligned root messages to error level in btrfs_validate_super()
btrfs: mark all error and warning checks as unlikely in btrfs_validate_super()
btrfs: pass transaction handle to write_all_supers()
btrfs: abort transaction on error in write_all_supers()
btrfs: tag error branches as unlikely during super block writes
btrfs: remove max_mirrors argument from write_all_supers()
btrfs: set written super flag once in write_all_supers()
fs/btrfs/disk-io.c | 167 +++++++++++++++++++----------------------
fs/btrfs/disk-io.h | 2 +-
fs/btrfs/transaction.c | 2 +-
fs/btrfs/tree-log.c | 2 +-
4 files changed, 82 insertions(+), 91 deletions(-)
--
2.47.2
next reply other threads:[~2026-02-04 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 15:51 fdmanana [this message]
2026-02-04 15:51 ` [PATCH 1/7] btrfs: change unaligned root messages to error level in btrfs_validate_super() fdmanana
2026-02-04 15:51 ` [PATCH 2/7] btrfs: mark all error and warning checks as unlikely " fdmanana
2026-02-05 12:04 ` David Sterba
2026-02-04 15:52 ` [PATCH 3/7] btrfs: pass transaction handle to write_all_supers() fdmanana
2026-02-04 15:52 ` [PATCH 4/7] btrfs: abort transaction on error in write_all_supers() fdmanana
2026-02-04 15:52 ` [PATCH 5/7] btrfs: tag error branches as unlikely during super block writes fdmanana
2026-02-04 15:52 ` [PATCH 6/7] btrfs: remove max_mirrors argument from write_all_supers() fdmanana
2026-02-08 15:49 ` Chris Mason
2026-02-08 18:24 ` Filipe Manana
2026-02-04 15:52 ` [PATCH 7/7] btrfs: set written super flag once in write_all_supers() fdmanana
2026-02-05 12:04 ` [PATCH 0/7] btrfs: minor tweaks and cleanups to the super block writing path David Sterba
2026-02-05 21:12 ` 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.1770212626.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.