From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>,
Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org, xfs@oss.sgi.com
Subject: XFS reflink and development tip git trees updated
Date: Sun, 4 Sep 2016 22:33:17 -0700 [thread overview]
Message-ID: <20160905053317.GA15302@birch.djwong.org> (raw)
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-1 [17f66c42de]
https://github.com/djwong/xfsprogs/tree/for-dave-for-4.9-1 [7b015920a]
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.
I created these two branches partly because Brian was complaining about it
being a PITA to carve out a working branch. The patches haven't changed at all
since the giant mailing a couple of weeks ago.
-----------
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
Note that I'm in the middle of reworking the GETFSMAP ioctl to eliminate the
problems that Andreas pointed out last week, and reworking the getfsmap and
scrub code to eliminate buffer deadlocks when a btree loop exists, so the last
few patches are ... very scraggly.
--D
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-09-05 5:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 5:33 Darrick J. Wong [this message]
2016-09-09 5:24 ` XFS reflink and getfsmap/scrub development git trees updated again Darrick J. Wong
2016-09-19 16:11 ` XFS reflink and development tip git trees updated 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=20160905053317.GA15302@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--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).