public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
	Josef Bacik <josef@toxicpanda.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	"kernel-team@fb.com" <kernel-team@fb.com>,
	Filipe Manana <fdmanana@suse.com>,
	Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
	Naohiro Aota <Naohiro.Aota@wdc.com>,
	Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCH v5 3/3] btrfs: use buffer xarray for extent buffer writeback operations
Date: Thu, 29 May 2025 01:25:16 +0200	[thread overview]
Message-ID: <20250528232516.GL4037@twin.jikos.cz> (raw)
In-Reply-To: <h7tbeznpfl762xay6d4q72ghjqeqieqrhjvq3vk53oedm27yq2@ksw6k4ggrxwn>

On Mon, May 26, 2025 at 06:53:02AM +0000, Shinichiro Kawasaki wrote:
> On May 26, 2025 / 13:50, Qu Wenruo wrote:
> > 
> > 
> > 在 2025/5/26 10:47, Shinichiro Kawasaki 写道:
> > > On Apr 28, 2025 / 10:52, Josef Bacik wrote:
> > > > Currently we have this ugly back and forth with the btree writeback
> > > > where we find the folio, find the eb associated with that folio, and
> > > > then attempt to writeback.  This results in two different paths for
> > > > subpage eb's and >= pagesize eb's.
> > > > 
> > > > Clean this up by adding our own infrastructure around looking up tag'ed
> > > > eb's and writing the eb's out directly.  This allows us to unify the
> > > > subpage and >= pagesize IO paths, resulting in a much cleaner writeback
> > > > path for extent buffers.
> > > 
> > > [...]
> > > 
> > > When I ran blktests on the for-next kernel with the tag next-20250521, I
> > > observed the test case zdd/009 failed with repeated WARNs at
> > > release_extent_buffer() [1].
> > 
> > Unfortunately that's a known bug, fixed by this patch:
> > 
> > https://lore.kernel.org/linux-btrfs/b964b92f482453cbd122743995ff23aa7158b2cb.1747677774.git.josef@toxicpanda.com/
> > 
> 
> Ah, thank you for letting me know. I confirmed that the fix avoids the failure
> on my test system.

FYI, the fix is now in master.

      reply	other threads:[~2025-05-28 23:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-28 14:52 [PATCH v5 0/3] btrfs: simplify extent buffer writeback Josef Bacik
2025-04-28 14:52 ` [PATCH v5 1/3] btrfs: convert the buffer_radix to an xarray Josef Bacik
2025-05-07  9:31   ` Qu Wenruo
2025-04-28 14:52 ` [PATCH v5 2/3] btrfs: set DIRTY and WRITEBACK tags on the buffer_tree Josef Bacik
2025-04-28 14:52 ` [PATCH v5 3/3] btrfs: use buffer xarray for extent buffer writeback operations Josef Bacik
2025-05-26  1:17   ` Shinichiro Kawasaki
2025-05-26  4:20     ` Qu Wenruo
2025-05-26  6:53       ` Shinichiro Kawasaki
2025-05-28 23:25         ` David Sterba [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=20250528232516.GL4037@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=Damien.LeMoal@wdc.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=Naohiro.Aota@wdc.com \
    --cc=fdmanana@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=shinichiro.kawasaki@wdc.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