linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	clm@fb.com, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fix for 4.20-rc5
Date: Wed,  5 Dec 2018 14:34:01 +0100	[thread overview]
Message-ID: <cover.1544016523.git.dsterba@suse.com> (raw)

Hi,

a patch in 4.19 introduced a sanity check that was too strict and a
filesystem cannot be mounted. This happens for filesystems with more
than 10 devices and has been reported a few users so we need the fix to
propagate to stable. Please pull, thanks.

----------------------------------------------------------------
The following changes since commit 42a657f57628402c73237547f0134e083e2f6764:

  btrfs: relocation: set trans to be NULL after ending transaction (2018-11-23 13:47:46 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.20-rc5-tag

for you to fetch changes up to 10950929e994c5ecee149ff0873388d3c98f12b5:

  btrfs: tree-checker: Don't check max block group size as current max chunk size limit is unreliable (2018-12-04 15:05:30 +0100)

----------------------------------------------------------------
Qu Wenruo (1):
      btrfs: tree-checker: Don't check max block group size as current max chunk size limit is unreliable

 fs/btrfs/tree-checker.c | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

             reply	other threads:[~2018-12-05 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 13:34 David Sterba [this message]
2018-12-05 18:20 ` [GIT PULL] Btrfs fix for 4.20-rc5 pr-tracker-bot

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=cover.1544016523.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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).