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 for 4.13, part 2
Date: Fri, 14 Jul 2017 22:16:12 +0200 [thread overview]
Message-ID: <cover.1500058584.git.dsterba@suse.com> (raw)
Hi,
we've identified and fixed a silent corruption (introduced by code in the
first pull), a fixup after the blk_status_t merge and two fixes to incremental
send that Filipe has been hunting for some time. Please pull, thanks.
----------------------------------------------------------------
The following changes since commit 848c23b78fafdcd3270b06a30737f8dbd70c347f:
btrfs: Remove false alert when fiemap range is smaller than on-disk extent (2017-06-29 20:25:20 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.13-part2
for you to fetch changes up to c3cfb656307583ddfea45375c10183737593c195:
Btrfs: fix unexpected return value of bio_readpage_error (2017-07-14 20:42:37 +0200)
----------------------------------------------------------------
David Sterba (3):
Merge branch 'next/filipe' into for-4.13-part2
btrfs: cloned bios must not be iterated by bio_for_each_segment_all
btrfs: btrfs_create_repair_bio never fails, skip error handling
Filipe Manana (3):
Btrfs: incremental send, fix invalid path for link commands
Btrfs: incremental send, fix invalid memory access
Btrfs: fix write corruption due to bio cloning on raid5/6
Liu Bo (1):
Btrfs: fix unexpected return value of bio_readpage_error
fs/btrfs/compression.c | 1 +
fs/btrfs/disk-io.c | 1 +
fs/btrfs/extent_io.c | 19 ++++++-----
fs/btrfs/extent_io.h | 4 +--
fs/btrfs/inode.c | 6 ++--
fs/btrfs/raid56.c | 26 ++++++++++-----
fs/btrfs/send.c | 88 +++++++++++++++++++++++++++++++-------------------
7 files changed, 88 insertions(+), 57 deletions(-)
reply other threads:[~2017-07-14 20:17 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.1500058584.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).