public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Burkov <boris@bur.io>
To: Daniel Vacek <neelx@suse.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: correct the assert for subpage case
Date: Mon, 12 May 2025 10:53:53 -0700	[thread overview]
Message-ID: <20250512175353.GA3472716@zen.localdomain> (raw)
In-Reply-To: <20250512132850.2973032-1-neelx@suse.com>

On Mon, May 12, 2025 at 03:28:50PM +0200, Daniel Vacek wrote:
> 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>

I would lean towards removing it, personally. But LGTM, thanks.

Reviewed-by: Boris Burkov <boris@bur.io>

> ---
>  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;
>  	}
> -- 
> 2.47.2
> 

  reply	other threads:[~2025-05-12 17:53 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 [this message]
2025-05-13  7:50   ` Daniel Vacek
2025-05-12 22:40 ` Qu Wenruo

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=20250512175353.GA3472716@zen.localdomain \
    --to=boris@bur.io \
    --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