From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v4 0/3] btrfs: fix an ASSERT() triggered inside prepare_to_merge()
Date: Wed, 9 Aug 2023 21:42:20 +0200 [thread overview]
Message-ID: <ZNPsHMUPvmw5usqB@twin.jikos.cz> (raw)
In-Reply-To: <cover.1691054362.git.wqu@suse.com>
On Thu, Aug 03, 2023 at 05:20:40PM +0800, Qu Wenruo wrote:
> [CHANGELOG]
> v4:
> - Remove the remaining commas inside the root key prompt of the 2nd
> patch
Patches added to misc-next, with the WARN_ONs for now but I'd really
like to get them removed once we discuss it.
prev parent reply other threads:[~2023-08-09 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 9:20 [PATCH v4 0/3] btrfs: fix an ASSERT() triggered inside prepare_to_merge() Qu Wenruo
2023-08-03 9:20 ` [PATCH v4 1/3] btrfs: avoid race with qgroup tree creation and relocation Qu Wenruo
2023-08-03 9:20 ` [PATCH v4 2/3] btrfs: exit gracefully if reloc roots don't match Qu Wenruo
2023-08-03 10:26 ` Filipe Manana
2023-08-09 19:24 ` David Sterba
2023-08-10 0:57 ` Qu Wenruo
2023-08-17 12:44 ` David Sterba
2023-08-03 9:20 ` [PATCH v4 3/3] btrfs: reject invalid reloc tree root keys with stack dump Qu Wenruo
2023-08-09 19:42 ` 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=ZNPsHMUPvmw5usqB@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--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