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.18-rc5
Date: Sat, 21 Jul 2018 07:32:44 +0200 [thread overview]
Message-ID: <cover.1532150370.git.dsterba@suse.com> (raw)
Hi,
please pull the following update to btrfs. It's a fix of a corruption
regarding fsync and clone, under some very specific conditions explained
in the patch. The fix is marked for stable 3.16+ so I'd like to get it
merged now given the impact. Thanks.
----------------------------------------------------------------
The following changes since commit 665d4953cde6d9e75c62a07ec8f4f8fd7d396ade:
btrfs: scrub: Don't use inode page cache in scrub_handle_errored_block() (2018-07-17 13:56:30 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.18-rc5-tag
for you to fetch changes up to bd3599a0e142cd73edd3b6801068ac3f48ac771a:
Btrfs: fix file data corruption after cloning a range and fsync (2018-07-19 15:36:31 +0200)
----------------------------------------------------------------
Filipe Manana (1):
Btrfs: fix file data corruption after cloning a range and fsync
fs/btrfs/extent_io.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
reply other threads:[~2018-07-21 5:35 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.1532150370.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).