From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/6] btrfs: preparation patches for the incoming metadata folio conversion
Date: Fri, 14 Jul 2023 00:03:11 +0200 [thread overview]
Message-ID: <20230713220311.GC20457@suse.cz> (raw)
In-Reply-To: <9251d155-2e2e-a126-579e-2765e98a4a9d@gmx.com>
On Fri, Jul 14, 2023 at 05:30:33AM +0800, Qu Wenruo wrote:
> On 2023/7/14 00:39, David Sterba wrote:
> > ref#0: tree block backref root 7
> > item 14 key (30572544 169 0) itemoff 15815 itemsize 33
> > extent refs 1 gen 5 flags 2
> > ref#0: tree block backref root 7
> > item 15 key (30588928 169 0) itemoff 15782 itemsize 33
> > extent refs 1 gen 5 flags 2
> > ref#0: tree block backref root 7
>
> This looks like an error in memmove_extent_buffer() which I
> intentionally didn't touch.
>
> Anyway I'll try rebase and more tests.
>
> Can you put your modified commits in an external branch so I can inherit
> all your modifications?
First I saw the crashes with the modified patches but the report is from
what you sent to the mailinglist so I can eliminate error on my side.
next prev parent reply other threads:[~2023-07-13 22:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 6:37 [PATCH v2 0/6] btrfs: preparation patches for the incoming metadata folio conversion Qu Wenruo
2023-07-12 6:37 ` [PATCH v2 1/6] btrfs: tests: enhance extent buffer bitmap tests Qu Wenruo
2023-07-12 6:37 ` [PATCH v2 2/6] btrfs: refactor extent buffer bitmaps operations Qu Wenruo
2023-07-13 11:53 ` David Sterba
2023-07-12 6:37 ` [PATCH v2 3/6] btrfs: use write_extent_buffer() to implement write_extent_buffer_*id() Qu Wenruo
2023-07-12 6:37 ` [PATCH v2 4/6] btrfs: refactor memcpy_extent_buffer() Qu Wenruo
2023-07-13 11:51 ` David Sterba
2023-07-12 6:37 ` [PATCH v2 5/6] btrfs: refactor copy_extent_buffer_full() Qu Wenruo
2023-07-12 6:37 ` [PATCH v2 6/6] btrfs: call copy_extent_buffer_full() inside btrfs_clone_extent_buffer() Qu Wenruo
2023-07-13 11:55 ` David Sterba
2023-07-12 6:44 ` [PATCH v2 0/6] btrfs: preparation patches for the incoming metadata folio conversion Sweet Tea Dorminy
2023-07-12 16:41 ` Christoph Hellwig
2023-07-12 23:58 ` Qu Wenruo
2023-07-13 11:16 ` Christoph Hellwig
2023-07-13 11:26 ` David Sterba
2023-07-13 11:41 ` Qu Wenruo
2023-07-13 11:49 ` David Sterba
2023-07-13 12:09 ` David Sterba
2023-07-13 16:39 ` David Sterba
2023-07-13 21:30 ` Qu Wenruo
2023-07-13 22:03 ` David Sterba [this message]
2023-07-14 0:09 ` Qu Wenruo
2023-07-14 0:26 ` David Sterba
2023-07-14 1:58 ` Qu Wenruo
2023-07-14 10:03 ` David Sterba
2023-07-14 10:32 ` Qu Wenruo
2023-07-14 10:41 ` David Sterba
2023-07-15 0:39 ` Qu Wenruo
2023-07-15 1:02 ` 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=20230713220311.GC20457@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--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