From: Wang Yugui <wangyugui@e16-tech.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v3 0/7] extent buffer dirty cleanups
Date: Fri, 27 Jan 2023 19:27:48 +0800 [thread overview]
Message-ID: <20230127192747.9C88.409509F4@e16-tech.com> (raw)
In-Reply-To: <cover.1674766637.git.josef@toxicpanda.com>
Hi,
> v2->v3:
> - Reworked the logic around clearing dirty on extent buffers not in our
> transaction. We do need this for update_ref_for_cow in some cases that I
> didn't account for. I've expanded the logic for this make it more idiot
> proof, and adjusted all of the patches accordingly.
The issue reported for v2 have been fixed. Thanks a lot.
no regression have been found for these v3 patches here.
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2023/01/27
>
> v1->v2:
> - Added "btrfs: do not call btrfs_clean_tree_block in update_ref_for_cow", Qu
> noticed some corruption with the original patchset, this turned out to be
> because we were clearing the extent buffer dirty at cow time, which doesn't
> make sense as we're not free'ing the current block in our current transaction.
>
> --- Original email ---
> Hello,
>
> While sync'ing ctree.c to btrfs-progs I noticed we have some oddities when it
> comes to how we deal with the extent buffer being dirty. We have
> btrfs_clean_tree_block, which is sort of meant to be run against extent buffers
> we've modified in this transaction. However we have some other places where
> we've open coded the same work without the generation check. This makes it kind
> of confusing, and is inconsistent with how we deal with the
> fs_info->dirty_metadata_bytes.
>
> So clean this stuff up so we have one helper we use for setting the extent
> buffer dirty (btrfs_mark_buffer_dirty) and one for clearing dirty
> (btrfs_clear_buffer_dirty). This makes everything more consistent and clean
> across the board. I've additionally cleaned up a random writeback thing we had
> in tree-log that I noticed while doing these cleanups. Thanks,
>
> Josef
>
> Josef Bacik (7):
> btrfs: always lock the block before calling btrfs_clean_tree_block
> btrfs: add trans argument to btrfs_clean_tree_block
> btrfs: replace clearing extent buffer dirty bit with btrfs_clean_block
> btrfs: do not increment dirty_metadata_bytes in set_btree_ioerr
> btrfs: rename btrfs_clean_tree_block => btrfs_clear_buffer_dirty
> btrfs: combine btrfs_clear_buffer_dirty and clear_extent_buffer_dirty
> btrfs: remove btrfs_wait_tree_block_writeback
>
> fs/btrfs/ctree.c | 31 +++++++++++++++--------------
> fs/btrfs/disk-io.c | 25 +++++-------------------
> fs/btrfs/disk-io.h | 3 ++-
> fs/btrfs/extent-tree.c | 9 ++++-----
> fs/btrfs/extent_io.c | 23 ++++++++++++++--------
> fs/btrfs/extent_io.h | 5 ++++-
> fs/btrfs/free-space-tree.c | 2 +-
> fs/btrfs/ioctl.c | 2 +-
> fs/btrfs/qgroup.c | 2 +-
> fs/btrfs/tree-log.c | 40 ++++++++++++++------------------------
> 10 files changed, 64 insertions(+), 78 deletions(-)
>
> --
> 2.26.3
next prev parent reply other threads:[~2023-01-27 11:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 21:00 [PATCH v3 0/7] extent buffer dirty cleanups Josef Bacik
2023-01-26 21:00 ` [PATCH v3 1/7] btrfs: always lock the block before calling btrfs_clean_tree_block Josef Bacik
2023-01-26 21:00 ` [PATCH v3 2/7] btrfs: add trans argument to btrfs_clean_tree_block Josef Bacik
2023-01-26 21:00 ` [PATCH v3 3/7] btrfs: replace clearing extent buffer dirty bit with btrfs_clean_block Josef Bacik
2023-01-26 21:00 ` [PATCH v3 4/7] btrfs: do not increment dirty_metadata_bytes in set_btree_ioerr Josef Bacik
2023-01-26 21:00 ` [PATCH v3 5/7] btrfs: rename btrfs_clean_tree_block => btrfs_clear_buffer_dirty Josef Bacik
2023-01-26 21:00 ` [PATCH v3 6/7] btrfs: combine btrfs_clear_buffer_dirty and clear_extent_buffer_dirty Josef Bacik
2023-01-26 21:01 ` [PATCH v3 7/7] btrfs: remove btrfs_wait_tree_block_writeback Josef Bacik
2023-01-27 11:27 ` Wang Yugui [this message]
2023-02-06 17:12 ` [PATCH v3 0/7] extent buffer dirty cleanups 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=20230127192747.9C88.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=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