linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eryu Guan <eguan@redhat.com>
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 5/5] xfs: test fuzzing every field of a dquot
Date: Thu, 24 Aug 2017 10:37:18 -0700	[thread overview]
Message-ID: <20170824173718.GG4796@magnolia> (raw)
In-Reply-To: <20170824090335.GM31418@eguan.usersys.redhat.com>

On Thu, Aug 24, 2017 at 05:03:35PM +0800, Eryu Guan wrote:
> On Fri, Jul 21, 2017 at 03:04:58PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> > 
> > See what happens when we fuzz every field of a quota information structure.
> > 
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> 
> These tests all failed in the same way like:
> 
>     +scrub didn't fail with diskdq.magic = zeroes.
>     +scrub didn't fail with diskdq.magic = ones.
>     +scrub didn't fail with diskdq.magic = firstbit.
>     +scrub didn't fail with diskdq.magic = middlebit.
>     ...
> 
> with 4.13-rc5 kernel and xfsprogs for-next branch. I assume that's
> something need to be fixed in the kernel?

Yes, that's testing whether or not online scrub actually notices when
we corrupt something.  I'll look into it, but output like that is a sign
that the test is working as designed. :)

--D

> 
> ...
> 
> > diff --git a/tests/xfs/1382 b/tests/xfs/1382
> > new file mode 100755
> > index 0000000..fd7e50d
> > --- /dev/null
> > +++ b/tests/xfs/1382
> > @@ -0,0 +1,63 @@
> > +#! /bin/bash
> > +# FS QA Test No. 1380
>                     ^^^^ I changed it to 1382 then renumbered.
> 
> Thanks,
> Eryu
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-08-24 17:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 22:04 [PATCH 0/5] miscellaneous tests Darrick J. Wong
2017-07-21 22:04 ` [PATCH 1/5] xfs: only run scrub in dry run mode Darrick J. Wong
2017-07-21 22:04 ` [PATCH 2/5] ext4: fsmap tests Darrick J. Wong
2017-07-21 22:04 ` [PATCH 3/5] common/inject: refactor helpers to use new errortag interface Darrick J. Wong
2017-08-02  8:37   ` Eryu Guan
2017-08-02 14:30     ` Brian Foster
2017-08-02 15:52       ` Darrick J. Wong
2017-08-02 16:29         ` Brian Foster
2017-08-03  0:56         ` Eryu Guan
2017-08-03 15:49   ` [PATCH v2 " Darrick J. Wong
2017-08-04  0:45     ` Eryu Guan
2017-08-04 15:32       ` Darrick J. Wong
2017-08-04 15:37   ` [PATCH v3 " Darrick J. Wong
2017-07-21 22:04 ` [PATCH 4/5] common/populate: enable xfs quota accounting Darrick J. Wong
2017-08-04  1:54   ` Eryu Guan
2017-08-08 21:24     ` Darrick J. Wong
2017-08-04  2:22   ` Eryu Guan
2017-08-08 21:22     ` Darrick J. Wong
2017-08-23 22:03       ` Darrick J. Wong
2017-08-24  3:23         ` Eryu Guan
2017-07-21 22:04 ` [PATCH 5/5] xfs: test fuzzing every field of a dquot Darrick J. Wong
2017-08-24  9:03   ` Eryu Guan
2017-08-24 17:37     ` Darrick J. Wong [this message]
2017-08-04  7:00 ` [PATCH 0/5] miscellaneous tests Eryu Guan

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=20170824173718.GG4796@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=eguan@redhat.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).