On Thu, Jul 05, 2018 at 10:08:05PM -0700, Darrick J. Wong wrote: > On Fri, Jul 06, 2018 at 12:31:09PM +0800, Eryu Guan wrote: > > On Tue, Jul 03, 2018 at 09:50:37PM -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> > > > > The "re-repair" failures are gone, but I still see some test failures > > like (xfs/1398 for example) > > > > +re-mount failed (32) with magic = zeroes. > > +re-mount failed (32) with magic = ones. > > ... > > > > Looks like the re-mount is expected to fail as we skipped all the repair work. > > Yeah, these tests are going to throw a /lot/ of errors as we try to see > if we can get the kernel to blow up on deliberately garbage filesystems. > They're not expected to pass ever, except in the sense that the kernel > doesn't just crash. :) > > > Also, there're _check_dmesg failures too (they were buried among other > > failures so I didn't notice them in last review), like this "Internal > > error" from xfs/1397 > > But yeah, I will add _check_dmesg to all of the tests before the next > submission (unless you commit it before then). I'll wait for re-submission :) 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
