From: Dave Chinner <david@fromorbit.com>
To: gregkh@linuxfoundation.org
Cc: djwong@kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, sandeen@sandeen.net
Subject: [GIT PULL] xfs: fixes for v4.19-rc7
Date: Thu, 11 Oct 2018 10:55:34 +1100 [thread overview]
Message-ID: <20181010235534.GA8838@dastard> (raw)
Hi Greg,
Can you please pull the XFS update from the tag listed below? This
contains the fix for the clone_file_range data corruption issue I
mentioned in my -rc6 pull request (zero post-eof blocks), as well as
fixes for several other equally serious problems we found while
auditing the clone/dedupe ioctls for other issues. The rest of the
problems we found (there were a *lot*) will be addressed in the 4.20
cycle.
Cheers,
Dave.
The following changes since commit e55ec4ddbef9897199c307dfb23167e3801fdaf5:
xfs: fix error handling in xfs_bmap_extents_to_btree (2018-10-01 08:11:07 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux tags/xfs-fixes-for-4.19-rc7
for you to fetch changes up to b39989009bdb84992915c9869f58094ed5becf10:
xfs: fix data corruption w/ unaligned reflink ranges (2018-10-06 11:44:39 +1000)
----------------------------------------------------------------
xfs: fixes for 4.19-rc7
Update for 4.19-rc7 to fix numerous file clone and deduplication issues.
----------------------------------------------------------------
Darrick J. Wong (3):
xfs: refactor clonerange preparation into a separate helper
xfs: zero posteof blocks when cloning above eof
xfs: update ctime and remove suid before cloning files
Dave Chinner (2):
xfs: fix data corruption w/ unaligned dedupe ranges
xfs: fix data corruption w/ unaligned reflink ranges
fs/xfs/xfs_reflink.c | 200 ++++++++++++++++++++++++++++++++++++++++++---------
1 file changed, 165 insertions(+), 35 deletions(-)
--
Dave Chinner
david@fromorbit.com
next reply other threads:[~2018-10-10 23:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 23:55 Dave Chinner [this message]
2018-10-11 5:40 ` [GIT PULL] xfs: fixes for v4.19-rc7 Greg KH
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=20181010235534.GA8838@dastard \
--to=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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