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 fixes for 4.16-rc6
Date: Fri, 16 Mar 2018 15:10:37 +0100 [thread overview]
Message-ID: <cover.1521208695.git.dsterba@suse.com> (raw)
Hi,
there's an important revert in this pull request that needs to go to
stable as it causes a corruption on big endian machines. The other fix
is for FIEMAP incorrectly reporting shared extents before a sync and one
fix for a crash in raid56.
So far we got only one report about the BE corruption, the stable
kernels were out for like a week, so hopefully the scope of the damage
is low.
Please pull, thanks.
----------------------------------------------------------------
The following changes since commit 1f250e929a9c9332fd6ea34da684afee73837cfe:
Btrfs: fix log replay failure after unlink and link combination (2018-03-01 16:18:40 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.16-rc5-tag
for you to fetch changes up to 093e037ca88e1767693bc6bcb2df3f49c6be68c7:
Revert "btrfs: use proper endianness accessors for super_copy" (2018-03-16 14:49:44 +0100)
----------------------------------------------------------------
David Sterba (1):
Revert "btrfs: use proper endianness accessors for super_copy"
Dmitriy Gorokh (1):
btrfs: Fix NULL pointer exception in find_bio_stripe
Edmund Nadolski (1):
btrfs: add missing initialization in btrfs_check_shared
fs/btrfs/backref.c | 1 +
fs/btrfs/raid56.c | 1 +
fs/btrfs/sysfs.c | 8 +++++---
fs/btrfs/transaction.c | 20 ++++++++------------
4 files changed, 15 insertions(+), 15 deletions(-)
reply other threads:[~2018-03-16 14:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1521208695.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).