From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs-linux: for-next updated to b39989009bdb
Date: Tue, 9 Oct 2018 10:15:04 +1100 [thread overview]
Message-ID: <20181008231504.GE6311@dastard> (raw)
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
Hi folks,
The for-next branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated. This is an update with a bunch of important
reflink fixes intended for 4.19-rc7, so please update and test this
so I can send a pull request to greg before the end of the week.
-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 for-next
for you to fetch changes up to b39989009bdb84992915c9869f58094ed5becf10:
xfs: fix data corruption w/ unaligned reflink ranges (2018-10-06 11:44:39 +1000)
----------------------------------------------------------------
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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2018-10-09 6:29 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=20181008231504.GE6311@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.