From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>,
Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org, Brian Foster <bfoster@redhat.com>,
amir73il@gmail.com
Subject: XFS reflink trees updated for 4.9
Date: Sun, 2 Oct 2016 12:01:07 -0700 [thread overview]
Message-ID: <20161002190106.GC21076@birch.djwong.org> (raw)
Seeing as 4.8 is probably going out today, here's the latest for-4.9 branch:
https://github.com/djwong/linux/tree/for-dave-for-4.9-9
https://github.com/djwong/xfsprogs/tree/for-dave-for-4.9-9
https://github.com/djwong/xfstests/tree/djwong-devel
I've rolled up all the comment fixes that have come in this week.
Thanks to everyone who's reviewed the patches (Dave, Christoph, and
Brian come to mind)!
I've also sped up stale CoW staging extent recovery by stashing all
those records in the right side of the refcount btree per a suggestion
from Dave on Friday afternoon. It was a relatively small change, so
I didn't bother holding off, and everything still passes the same
tests they did before, AFAICT.
---
Dave: the two xfs_repair patches I posted yesterday are for xfsprogs
4.8. One fixes some garbled rmap code that crashed when we
overestimated the freespace btree space requirements in phase5, and
needs to go in before the release. The second patch re-adds the lost
blocks to the freesp btree so we get rid of those "sorry, lost XXX
blocks" messages. That one isn't so urgent.
--D
next reply other threads:[~2016-10-02 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 19:01 Darrick J. Wong [this message]
2016-10-03 17:21 ` XFS reflink trees updated for 4.9 Darrick J. Wong
2016-10-03 18:01 ` Christoph Hellwig
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=20161002190106.GC21076@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 \
/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).