From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Daniel Vacek <neelx@suse.com>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: correct the assert for subpage case
Date: Tue, 13 May 2025 08:10:54 +0930 [thread overview]
Message-ID: <a9ca69ae-fd11-45b1-997b-2186226214e0@gmx.com> (raw)
In-Reply-To: <20250512132850.2973032-1-neelx@suse.com>
在 2025/5/12 22:58, Daniel Vacek 写道:
> The assert is only true in !subpage case. We can either fix it this way
> or completely remove it.
>
> This fixes and should be folded into:
> btrfs: fix broken drop_caches on extent buffer folios
>
> Signed-off-by: Daniel Vacek <neelx@suse.com>
Looks good to me.
Although I agree with Boris, it's better to remove the ASSERT().
Subpage is no longer a corner/minor usage anymore, we shouldn't treat
subpage and normal cases differently when possible.
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> fs/btrfs/extent_io.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
> index 80a8563a25add..3b3f73894ffe2 100644
> --- a/fs/btrfs/extent_io.c
> +++ b/fs/btrfs/extent_io.c
> @@ -3411,7 +3411,7 @@ struct extent_buffer *alloc_extent_buffer(struct btrfs_fs_info *fs_info,
> continue;
> }
>
> - ASSERT(!folio_test_private(folio));
> + ASSERT(!btrfs_meta_is_subpage(fs_info) && !folio_test_private(folio));
> folio_put(folio);
> eb->folios[i] = NULL;
> }
prev parent reply other threads:[~2025-05-12 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 13:28 [PATCH] btrfs: correct the assert for subpage case Daniel Vacek
2025-05-12 17:53 ` Boris Burkov
2025-05-13 7:50 ` Daniel Vacek
2025-05-12 22:40 ` 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=a9ca69ae-fd11-45b1-997b-2186226214e0@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neelx@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