From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fix for 5.5-rc8
Date: Sat, 25 Jan 2020 13:14:00 +0100 [thread overview]
Message-ID: <cover.1579953624.git.dsterba@suse.com> (raw)
Hi,
here's a last minute fix for a regression introduced in this development
cycle. There's a small chance of a silent corruption when device replace
and NOCOW data writes happen at the same time in one block group.
Metadata or COW data writes are unaffected. The fixup patch is there to
silence an unnecessary warning.
Please pull, thanks.
----------------------------------------------------------------
The following changes since commit b35cf1f0bf1f2b0b193093338414b9bd63b29015:
btrfs: check rw_devices, not num_devices for balance (2020-01-17 15:40:54 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.5-rc8-tag
for you to fetch changes up to 4cea9037f82a6deed0f2f61e4054b7ae2519ef87:
btrfs: dev-replace: remove warning for unknown return codes when finished (2020-01-25 12:49:12 +0100)
----------------------------------------------------------------
David Sterba (1):
btrfs: dev-replace: remove warning for unknown return codes when finished
Qu Wenruo (1):
btrfs: scrub: Require mandatory block group RO for dev-replace
fs/btrfs/dev-replace.c | 5 +----
fs/btrfs/scrub.c | 33 ++++++++++++++++++++++++++++-----
2 files changed, 29 insertions(+), 9 deletions(-)
next reply other threads:[~2020-01-25 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 12:14 David Sterba [this message]
2020-01-25 19:05 ` [GIT PULL] Btrfs fix for 5.5-rc8 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.1579953624.git.dsterba@suse.com \
--to=dsterba@suse.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).