On Thu, Jun 28, 2018 at 11:10:27AM +0800, Eryu Guan wrote: > On Thu, Jun 21, 2018 at 11:32:55AM -0700, Darrick J. Wong wrote: > > From: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > > > > Fuzz every field of every structure and then try to write the > > filesystem, to see how many of these writes can crash the kernel. > > > > Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > > Almost all the tests here are failing in similar ways with v4.18-rc1 > kernel and latest xfsprogs from for-next branch, e.g. xfs/1423 fails as > > +re-repair failed (1) with diskdq.magic = zeroes. > +re-repair failed (1) with diskdq.magic = ones. > +re-repair failed (1) with diskdq.magic = firstbit. > +re-repair failed (1) with diskdq.magic = middlebit. > > Seems like we should skip re-repair in the "none" repair mode too in > __scratch_xfs_fuzz_field_test? Err, yep. I'll go fix that up too. :) --D > Thanks, > Eryu > -- > 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
