linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org, 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 22:10:15 +0800	[thread overview]
Message-ID: <0280e21f-e274-2f00-1743-cd250abf6d30@gmx.com> (raw)
In-Reply-To: <20181204135253.GR17773@twin.jikos.cz>


[-- Attachment #1.1: Type: text/plain, Size: 582 bytes --]



On 2018/12/4 下午9:52, David Sterba wrote:
> 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.
> 
> BTW, if there's an urgent fix or patch that should be considered for
> current devel cycle, please note that in the subject like
> 
>   [PATCH for 4.20-rc] btrfs: ...
> 
> to make it more visible.
> 

Great thanks for this hint!

Just forgot we have such tag.

Thanks,
Qu


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2018-12-04 14:10 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
2018-12-04 13:52   ` David Sterba
2018-12-04 14:10     ` Qu Wenruo [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=0280e21f-e274-2f00-1743-cd250abf6d30@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --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).