From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 00/10] btrfs-progs: prep work for syncing ctree.c
Date: Wed, 19 Apr 2023 17:20:40 -0400 [thread overview]
Message-ID: <cover.1681939107.git.josef@toxicpanda.com> (raw)
Hello,
These patches update a lot of the different ctree.c related helpers that have
diverged from the kernel in order to make ite easier syncing ctree.c directly.
This also syncs locking.[ch], but this is to just stub out the locking. This
will make it easier to sync ctree.c as well since there's locking in the kernel
that didn't exist when we had this in btrfs-progs.
This series depends on
btrfs-progs: prep work for syncing files into kernel-shared
btrfs-progs: sync basic code from the kernel
Thanks,
Josef
Josef Bacik (10):
btrfs-progs: const-ify the extent buffer helpers
btrfs-progs: bring root->state into btrfs-progs
btrfs-progs: rename btrfs_alloc_free_block to btrfs_alloc_tree_block
btrfs-progs: sync locking.h and stub out all the helpers
btrfs-progs: add btrfs_locking_nest to btrfs_alloc_tree_block
btrfs-progs: add some missing extent buffer helpers
btrfs-progs: rename btrfs_set_block_flags ->
btrfs_set_disk_extent_flags
btrfs-progs: cleanup args for btrfs_set_disk_extent_flags
btrfs-progs: rename clear_extent_buffer_dirty =>
btrfs_clear_buffer_dirty
btrfs-progs: make __btrfs_cow_block static
Makefile | 1 +
check/main.c | 7 +-
cmds/rescue-chunk-recover.c | 4 +-
cmds/rescue.c | 2 +-
include/kerncompat.h | 4 +
kernel-shared/ctree.c | 72 +++++-----
kernel-shared/ctree.h | 82 ++++++++++--
kernel-shared/disk-io.c | 33 +++--
kernel-shared/extent-tree.c | 28 ++--
kernel-shared/extent_io.c | 28 ++--
kernel-shared/extent_io.h | 15 ++-
kernel-shared/locking.c | 22 +++
kernel-shared/locking.h | 258 ++++++++++++++++++++++++++++++++++++
kernel-shared/transaction.c | 4 +-
14 files changed, 464 insertions(+), 96 deletions(-)
create mode 100644 kernel-shared/locking.c
create mode 100644 kernel-shared/locking.h
--
2.40.0
next reply other threads:[~2023-04-19 21:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 21:20 Josef Bacik [this message]
2023-04-19 21:20 ` [PATCH 01/10] btrfs-progs: const-ify the extent buffer helpers Josef Bacik
2023-04-19 21:20 ` [PATCH 02/10] btrfs-progs: bring root->state into btrfs-progs Josef Bacik
2023-04-19 21:20 ` [PATCH 03/10] btrfs-progs: rename btrfs_alloc_free_block to btrfs_alloc_tree_block Josef Bacik
2023-04-19 21:20 ` [PATCH 04/10] btrfs-progs: sync locking.h and stub out all the helpers Josef Bacik
2023-04-19 21:20 ` [PATCH 05/10] btrfs-progs: add btrfs_locking_nest to btrfs_alloc_tree_block Josef Bacik
2023-04-19 21:20 ` [PATCH 06/10] btrfs-progs: add some missing extent buffer helpers Josef Bacik
2023-04-19 21:20 ` [PATCH 07/10] btrfs-progs: rename btrfs_set_block_flags -> btrfs_set_disk_extent_flags Josef Bacik
2023-04-19 21:20 ` [PATCH 08/10] btrfs-progs: cleanup args for btrfs_set_disk_extent_flags Josef Bacik
2023-04-19 21:20 ` [PATCH 09/10] btrfs-progs: rename clear_extent_buffer_dirty => btrfs_clear_buffer_dirty Josef Bacik
2023-04-19 21:20 ` [PATCH 10/10] btrfs-progs: make __btrfs_cow_block static Josef Bacik
2023-05-03 9:54 ` [PATCH 00/10] btrfs-progs: prep work for syncing ctree.c David Sterba
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.1681939107.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 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.