From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 00/11] btrfs: add snapshot_id to btrfs_header and root_item
Date: Mon, 7 Mar 2022 17:36:50 -0500 [thread overview]
Message-ID: <cover.1646692474.git.josef@toxicpanda.com> (raw)
Hello,
This is the next series of changes for extent tree v2. This adds support for
the snapshot_id to the btrfs_header and btrfs_root_item. This will allow us to
track shared blocks more simply without requiring a lot of reference updates.
There are also a few extra patches tacked onto the end to add some more testing.
Since we're changing the size of the btrfs_header I wanted to get as much
coverage as possible on the different ways we modify leaves and nodes so I added
another selftest and added support for running the selftests with extent tree v2
set.
Thanks,
Josef
Josef Bacik (11):
btrfs: take into account BTRFS_HEADER_FLAG_V2 in the item/node helpers
btrfs: add global_tree_id to btrfs_root_item
btrfs: add snapshot_id to the btrfs_root_item
btrfs: handle the new snapshot_id field properly
btrfs: add a sanity checker for the header flags
btrfs: zero dummy extent buffers
btrfs: zero out temporary superblock buffer header
btrfs: add a debug range check for header_v2
btrfs: selftests: add a test for delete_one_dir_name
btrfs: don't do the global_id thing if we are a DUMMY_FS_INFO
btrfs: selftests: run with EXTENT_TREE_V2 set as well
fs/btrfs/ctree.c | 13 +-
fs/btrfs/ctree.h | 14 +-
fs/btrfs/disk-io.c | 4 +
fs/btrfs/extent-tree.c | 7 +
fs/btrfs/extent_io.c | 22 +++
fs/btrfs/tests/btrfs-tests.c | 77 +++++++----
fs/btrfs/tests/btrfs-tests.h | 18 ++-
fs/btrfs/tests/extent-buffer-tests.c | 181 ++++++++++++++++++++++++-
fs/btrfs/tests/extent-io-tests.c | 9 +-
fs/btrfs/tests/extent-map-tests.c | 2 +-
fs/btrfs/tests/free-space-tests.c | 6 +-
fs/btrfs/tests/free-space-tree-tests.c | 21 +--
fs/btrfs/tests/inode-tests.c | 25 ++--
fs/btrfs/tests/qgroup-tests.c | 5 +-
fs/btrfs/tree-checker.c | 27 ++++
fs/btrfs/volumes.c | 2 +
include/uapi/linux/btrfs_tree.h | 12 +-
17 files changed, 376 insertions(+), 69 deletions(-)
--
2.26.3
next reply other threads:[~2022-03-07 22:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 22:36 Josef Bacik [this message]
2022-03-07 22:36 ` [PATCH 01/11] btrfs: take into account BTRFS_HEADER_FLAG_V2 in the item/node helpers Josef Bacik
2022-03-07 22:36 ` [PATCH 02/11] btrfs: add global_tree_id to btrfs_root_item Josef Bacik
2022-03-07 22:36 ` [PATCH 03/11] btrfs: add snapshot_id to the btrfs_root_item Josef Bacik
2022-03-07 22:36 ` [PATCH 04/11] btrfs: handle the new snapshot_id field properly Josef Bacik
2022-03-07 22:36 ` [PATCH 05/11] btrfs: add a sanity checker for the header flags Josef Bacik
2022-03-07 22:36 ` [PATCH 06/11] btrfs: zero dummy extent buffers Josef Bacik
2022-03-07 22:36 ` [PATCH 07/11] btrfs: zero out temporary superblock buffer header Josef Bacik
2022-03-07 22:36 ` [PATCH 08/11] btrfs: add a debug range check for header_v2 Josef Bacik
2022-03-07 22:36 ` [PATCH 09/11] btrfs: selftests: add a test for delete_one_dir_name Josef Bacik
2022-03-07 22:37 ` [PATCH 10/11] btrfs: don't do the global_id thing if we are a DUMMY_FS_INFO Josef Bacik
2022-03-07 22:37 ` [PATCH 11/11] btrfs: selftests: run with EXTENT_TREE_V2 set as well Josef Bacik
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.1646692474.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox