From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>,
Brian Foster <bfoster@redhat.com>, Theodore Ts'o <tytso@mit.edu>
Cc: linux-xfs@vger.kernel.org, xfs@oss.sgi.com,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: XFS reflink and getfsmap/scrub development git trees updated again
Date: Thu, 8 Sep 2016 22:24:13 -0700 [thread overview]
Message-ID: <20160909052413.GD9314@birch.djwong.org> (raw)
In-Reply-To: <20160905053317.GA15302@birch.djwong.org>
Hi everyone,
I've just rebased the reflink patches against kernel 4.8-rc5 and the xfsprogs
dev branch:
https://github.com/djwong/linux/tree/for-dave-for-4.9-2
https://github.com/djwong/xfsprogs/tree/for-dave-for-4.9-2
These branches should contain /only/ the patches needed to get reflink working:
no fsmap ioctl, no online scrub, and no realtime rmapbt. I'm publishing these
branches in the hopes of getting wider testing prior to the merge window. I
haven't heard any complaints for several weeks now. The only changes since
4.9-1 are to take care of all the comments that Christoph has sent up to
this point.
-----------
For the latest development branch, check out the djwong-wtf branches on github:
https://github.com/djwong/linux/tree/djwong-wtf
https://github.com/djwong/xfsprogs/tree/djwong-wtf
This contains all the latest reflink patches, the reworked GETFSMAP ioctl,
and the latest online scrubbing code. The scraggly deadlock avoidance fixes
I mentioned in the last posting are now integrated properly into the patch
series. Also, btree left/right sibling pointer checks have been implemented.
(Adding Ted and the ext4 list because Ted expressed interest in GETFSMAP.)
--D
next prev parent reply other threads:[~2016-09-09 5:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 5:33 XFS reflink and development tip git trees updated Darrick J. Wong
2016-09-09 5:24 ` Darrick J. Wong [this message]
2016-09-19 16:11 ` Christoph Hellwig
2016-09-19 16:26 ` Darrick J. Wong
2016-09-20 4:39 ` Darrick J. Wong
2016-09-27 5:23 ` Darrick J. Wong
2016-09-27 14:27 ` Christoph Hellwig
2016-09-27 15:36 ` Darrick J. Wong
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=20160909052413.GD9314@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xfs@oss.sgi.com \
/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).