Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 3/3] btrfs: update stale comment in __cow_file_range_inline()
Date: Mon, 15 Dec 2025 20:20:56 +1030	[thread overview]
Message-ID: <f2bec37c-0230-48d0-993a-157b4a9031cb@gmx.com> (raw)
In-Reply-To: <CAL3q7H6Vkz53Edf=i2+yKpqs7mQt_qqZiveV43L1qU8cK8WEvw@mail.gmail.com>



在 2025/12/15 20:19, Filipe Manana 写道:
> On Mon, Dec 15, 2025 at 9:47 AM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>>
>>
>> 在 2025/12/15 20:08, fdmanana@kernel.org 写道:
>>> From: Filipe Manana <fdmanana@suse.com>
>>>
>>> We mention that the reserved data space is page size aligned but that's
>>> not true anymore, as it's sector size aligned instead.
>>> In commit 0bb067ca64e3 ("btrfs: fix the qgroup data free range for inline
>>> data extents") we updated the amount passed to btrfs_qgroup_free_data()
>>> from page size to sector size, but forgot to update the comment.
>>>
>>> Signed-off-by: Filipe Manana <fdmanana@suse.com>
>>> ---
>>>    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 f1ead789146b..6ae36cc5bcda 100644
>>> --- a/fs/btrfs/inode.c
>>> +++ b/fs/btrfs/inode.c
>>> @@ -676,7 +676,7 @@ static noinline int __cow_file_range_inline(struct btrfs_inode *inode,
>>>        /*
>>>         * Don't forget to free the reserved space, as for inlined extent
>>>         * it won't count as data extent, free them directly here.
>>> -      * And at reserve time, it's always aligned to page size, so
>>> +      * And at reserve time, it's always aligned to sector size, so
>>>         * just free one page here.
>>
>> There is still a "page" reference here.
> 
> Ah yes, I will update it before pushing to for-next, thanks.

Oh, forgot my tag.

Reviewed-by: Qu Wenruo <wqu@suse.com>

Thanks,
Qu

> 
>>
>> Other than that it looks good to me.
>>
>> Thanks,
>> Qu
>>
>>>         *
>>>         * If we fallback to non-inline (ret == 1) due to -ENOSPC, then we need
>>


  reply	other threads:[~2025-12-15  9:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15  9:38 [PATCH 0/3] btrfs: fixes for inline extent fallback and error handling fdmanana
2025-12-15  9:38 ` [PATCH 1/3] btrfs: do not free data reservation in fallback from inline due to -ENOSPC fdmanana
2025-12-15  9:45   ` Qu Wenruo
2025-12-15  9:38 ` [PATCH 2/3] btrfs: fix reservation leak in some error paths when inserting inline extent fdmanana
2025-12-15  9:38 ` [PATCH 3/3] btrfs: update stale comment in __cow_file_range_inline() fdmanana
2025-12-15  9:47   ` Qu Wenruo
2025-12-15  9:49     ` Filipe Manana
2025-12-15  9:50       ` Qu Wenruo [this message]
2025-12-15 18:43 ` [PATCH 0/3] btrfs: fixes for inline extent fallback and error handling 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=f2bec37c-0230-48d0-993a-157b4a9031cb@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=fdmanana@kernel.org \
    --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