From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: tchou <tchou@synology.com>, linux-btrfs@vger.kernel.org
Cc: clm@fb.com, dsterba@suse.com
Subject: Re: [PATCH] btrfs: preallocate extent changeset before acquiring extent_io_tree lock
Date: Fri, 17 Apr 2026 16:45:48 +0930 [thread overview]
Message-ID: <97f74be3-1630-44b7-a1df-accfad5c4090@gmx.com> (raw)
In-Reply-To: <20260417064119.1316463-1-tchou@synology.com>
在 2026/4/17 16:11, tchou 写道:
> In btrfs_clear_extent_bit_changeset(), the extent changeset ulist may need
> to allocate new nodes. Currently, this can happen while holding the
> extent_io_tree->lock spinlock. Although ulist_prealloc() uses GFP_NOFS to
> avoid deadlock with filesystem reclaim, it's better to preallocate before
> acquiring the spinlock to:
>
> 1. Avoid potential allocation failures while holding the lock
> 2. Be consistent with set_extent_bit() which already preallocates both
> extent state and changeset before the spinlock
> 3. Reduce lock contention by not doing allocations under the lock
>
> Preallocate the changeset ulist node before acquiring the spinlock,
> mirroring the pattern used for extent state preallocation.
Missing the SoB line.
Otherwise looks good to me.
Thanks,
Qu
> ---
> fs/btrfs/extent-io-tree.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/btrfs/extent-io-tree.c b/fs/btrfs/extent-io-tree.c
> index 626702244809..b5ba650cdb55 100644
> --- a/fs/btrfs/extent-io-tree.c
> +++ b/fs/btrfs/extent-io-tree.c
> @@ -663,6 +663,9 @@ int btrfs_clear_extent_bit_changeset(struct extent_io_tree *tree, u64 start, u64
> */
> prealloc = alloc_extent_state(mask);
> }
> + /* Preallocate the extent changeset ulist node before acquiring spinlock. */
> + if (changeset)
> + extent_changeset_prealloc(changeset, mask);
>
> spin_lock(&tree->lock);
> if (cached_state) {
prev parent reply other threads:[~2026-04-17 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 6:41 [PATCH] btrfs: preallocate extent changeset before acquiring extent_io_tree lock tchou
2026-04-17 7:15 ` Qu Wenruo [this message]
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=97f74be3-1630-44b7-a1df-accfad5c4090@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tchou@synology.com \
/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