On Mon, Dec 04, 2017 at 05:34:22PM -0800, Darrick J. Wong wrote: > On Sun, Sep 03, 2017 at 08:31:50AM -0700, Darrick J. Wong wrote: > > On Sun, Sep 03, 2017 at 09:25:13AM +0200, Christoph Hellwig wrote: > > > Looks like this didn't make the 4.14 for-next branch either. I guess > > > we'll just consider it for the next round? > > > > Yes, it caused a number of new xfstests failures due to new ENOSPC > > messages in the golden output so I decided to defer action on it until > > someone can assess and fix the problems appropriately. The worst part > > was that the new failures are intermittent. > > Heh, a customer slammed right into this, so I'll try to pick up this > patch again and fix all the xfstests.... I fixed most of the auto group regressions with small fixes to xfstests, but xfs/013 is a problem because once we run out of space to create new dirX we simply get nothing. Will have to study the behavior of that test in more depth... --D > --D > > > --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 > -- > 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
