linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dave Chinner <david@fromorbit.com>,
	Brian Foster <bfoster@redhat.com>,
	linux-xfs@vger.kernel.org, xfs@oss.sgi.com, amir73il@gmail.com
Subject: XFS reflink and development tip git trees updated
Date: Mon, 26 Sep 2016 22:23:44 -0700	[thread overview]
Message-ID: <20160927052344.GD3059@birch.djwong.org> (raw)
In-Reply-To: <20160920043942.GE10172@birch.djwong.org>

Ok, here's this week's for-4.9 branch:

https://github.com/djwong/linux/tree/for-dave-for-4.9-5
https://github.com/djwong/xfsprogs/tree/for-dave-for-4.9-5

The kernel tree includes Christoph's fixes for copy-on-write,
refactoring of a refcount btree function to use _btree_query_range (and
inclusion of the required diff_two_keys/init_high_key helpers), and
removal of the (totally broken) always_cow debug switch.  It also
contains a new error injection point to make reflink fail with ENOSPC.

The xfsprogs tree incorporates the libxfs changes in the kernel tree
but is largely the same as last week's for-4.9-2 branch.  The only
change in userspace programs is that xfs_io can trigger the
above-mentioned error injection point.

---

The WTF trees have been rebased to 4.8-rc8 and xfsprogs for-next:
https://github.com/djwong/linux/tree/djwong-wtf
https://github.com/djwong/xfsprogs/tree/djwong-wtf

These two trees contain all the changes noted above as well as in-kernel
scrubbing of directory and extended attribute data.  xfs_scrub has been
modified to take advantage of them, and can now fall back a little more
gracefully when kernel scrubbing is unavailable.

(Note that the WTF tree doesn't reflect the iomap rework that's in the
4.9 for-next tree; I'll rebase WTF against 4.9 after the merge window
closes.  Unfortunately that's the only way to pick up scrub or realtime
rmap support.)

--D

  reply	other threads:[~2016-09-27  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 ` 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 [this message]
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=20160927052344.GD3059@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=amir73il@gmail.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).