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(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
