From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f67.google.com ([74.125.83.67]:35671 "EHLO mail-pg0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751065AbeF1DKc (ORCPT ); Wed, 27 Jun 2018 23:10:32 -0400 Date: Thu, 28 Jun 2018 11:10:27 +0800 From: Eryu Guan Subject: Re: [PATCH 4/4] xfs: fuzz every field of every structure and test kernel crashes Message-ID: <20180628031027.GR2780@desktop> References: <152960594943.26479.1457883867468749220.stgit@magnolia> <152960597579.26479.1694478608504574104.stgit@magnolia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <152960597579.26479.1694478608504574104.stgit@magnolia> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: "Darrick J. Wong" Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org On Thu, Jun 21, 2018 at 11:32:55AM -0700, Darrick J. Wong wrote: > From: Darrick J. Wong > > 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 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? Thanks, Eryu