From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: iamhswang@gmail.com, linux-btrfs@vger.kernel.org
Cc: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com, wqu@suse.com,
boris@bur.io, linux-kernel@vger.kernel.org,
Haisu Wang <haisuwang@tencent.com>
Subject: Re: [PATCH] btrfs: fix the length of reserved qgroup to free
Date: Tue, 8 Oct 2024 18:25:58 +1030 [thread overview]
Message-ID: <b677188b-b41b-4a3d-8598-61e8ccdef075@gmx.com> (raw)
In-Reply-To: <20241008064849.1814829-1-haisuwang@tencent.com>
在 2024/10/8 17:18, iamhswang@gmail.com 写道:
> From: Haisu Wang <haisuwang@tencent.com>
>
> The dealloc flag may be cleared and the extent won't reach the disk
> in cow_file_range when errors path. The reserved qgroup space is
> freed in commit 30479f31d44d ("btrfs: fix qgroup reserve leaks in
> cow_file_range"). However, the length of untouched region to free
> need to be adjusted with the region size.
>
> Fixes: 30479f31d44d ("btrfs: fix qgroup reserve leaks in cow_file_range")
> Signed-off-by: Haisu Wang <haisuwang@tencent.com>
Right, just several lines before that, we increased @start by
@cur_alloc_size if @extent_reserved is true.
So we can not directly use the old range size.
You can improve that one step further by not modifying @start just for
the error handling path, although that should be another patch.
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> fs/btrfs/inode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index b0ad46b734c3..5eefa2318fa8 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -1592,7 +1592,7 @@ static noinline int cow_file_range(struct btrfs_inode *inode,
> clear_bits |= EXTENT_CLEAR_DATA_RESV;
> extent_clear_unlock_delalloc(inode, start, end, locked_folio,
> &cached, clear_bits, page_ops);
> - btrfs_qgroup_free_data(inode, NULL, start, cur_alloc_size, NULL);
> + btrfs_qgroup_free_data(inode, NULL, start, end - start + 1, NULL);
> }
> return ret;
> }
next prev parent reply other threads:[~2024-10-08 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 6:48 iamhswang
2024-10-08 7:55 ` Qu Wenruo [this message]
2024-10-08 11:18 ` hs wang
2024-10-08 20:50 ` Qu Wenruo
2024-10-08 16:12 ` Boris Burkov
2024-10-09 2:40 ` hs wang
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=b677188b-b41b-4a3d-8598-61e8ccdef075@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=boris@bur.io \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=haisuwang@tencent.com \
--cc=iamhswang@gmail.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wqu@suse.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
all inboxes | Powered by JetHome®