linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: fuzz every field of every structure and test kernel crashes
Date: Fri, 6 Jul 2018 14:08:20 +0800	[thread overview]
Message-ID: <20180706060820.GE2780@desktop> (raw)
In-Reply-To: <20180706050805.GT32415@magnolia>

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@oracle.com>
> > > 
> > > 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@oracle.com>
> > 
> > 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

  reply	other threads:[~2018-07-06  6:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  4:50 [PATCH 0/2] fstests: fixes and new tests Darrick J. Wong
2018-07-04  4:50 ` [PATCH 1/2] generic: mread past eof shows nonzero contents Darrick J. Wong
2018-07-08 15:38   ` Christoph Hellwig
2018-07-09 16:24     ` Darrick J. Wong
2018-07-04  4:50 ` [PATCH 2/2] xfs: fuzz every field of every structure and test kernel crashes Darrick J. Wong
2018-07-06  4:31   ` Eryu Guan
2018-07-06  5:08     ` Darrick J. Wong
2018-07-06  6:08       ` Eryu Guan [this message]
2018-07-06 14:41   ` [PATCH v2 " Darrick J. Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180706060820.GE2780@desktop \
    --to=guaneryu@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).