On Sun, Oct 02, 2016 at 12:01:07PM -0700, Darrick J. Wong wrote: > 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 Rebased against yesterday's for-next: https://github.com/djwong/linux/tree/for-dave-for-4.9-10 https://github.com/djwong/xfsprogs/tree/for-dave-for-4.9-10 No code changes on my end, and seems to pass all the tests it did before. --D > > 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 > -- > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
