From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.cz>,
stable@vger.kernel.org
Subject: Re: [PATCH] btrfs: tree-checker: Don't check max block group size as current max chunk size limit is unreliable
Date: Tue, 4 Dec 2018 14:38:56 +0100 [thread overview]
Message-ID: <20181204133856.GQ17773@twin.jikos.cz> (raw)
In-Reply-To: <3cd7ba2f-377f-604e-5996-fbf5086b9843@gmx.com>
On Tue, Dec 04, 2018 at 06:15:13PM +0800, Qu Wenruo wrote:
> Gentle ping.
>
> Please put this patch into current release as the new block group size
> limit check introduced in v4.19 is causing at least 2 reports in mail list.
I see, on the way to 4.20-rc with stable tags. Thanks.
next prev parent reply other threads:[~2018-12-04 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 1:06 [PATCH] btrfs: tree-checker: Don't check max block group size as current max chunk size limit is unreliable Qu Wenruo
2018-12-04 10:15 ` Qu Wenruo
2018-12-04 13:38 ` David Sterba [this message]
2018-12-04 13:52 ` David Sterba
2018-12-04 14:10 ` 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=20181204133856.GQ17773@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).