public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Guangwen Feng <fenggw-fnst@cn.fujitsu.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs/083: disable dmesg check
Date: Sat, 30 Jan 2016 19:05:03 -0800	[thread overview]
Message-ID: <20160131030503.GB5849@birch.djwong.org> (raw)
In-Reply-To: <1454068444-23926-1-git-send-email-fenggw-fnst@cn.fujitsu.com>

On Fri, Jan 29, 2016 at 07:54:04PM +0800, Guangwen Feng wrote:
> This test fuzzes the metadata and accesses the corrupted fs later,
> which always produces error info in dmesg and causes test fail,
> so fix this.
> 
> Signed-off-by: Guangwen Feng <fenggw-fnst@cn.fujitsu.com>
> ---
>  tests/xfs/083 | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/tests/xfs/083 b/tests/xfs/083
> index 8e14e88..558b964 100755
> --- a/tests/xfs/083
> +++ b/tests/xfs/083
> @@ -102,6 +102,11 @@ scratch_repair() {
>  }
>  
>  rm -f $seqres.full
> +
> +# We will access the corrupted fs later, which always produces error
> +# info in dmesg. We do not want the test to fail because of this.
> +_disable_dmesg_check

What kind of message did you hit?  I'd thought that the checksum errors
didn't include any of the magic text that tripped _check_dmesg.

--D

> +
>  echo "See interesting results in $seqres.full" | sed -e "s,$RESULT_DIR,RESULT_DIR,g"
>  SRCDIR=`pwd`
>  test -z "${FUZZ_ARGS}" && FUZZ_ARGS="-3 -n 32"
> -- 
> 1.8.4.2
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" 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:[~2016-01-31  3:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 11:54 [PATCH] xfs/083: disable dmesg check Guangwen Feng
2016-01-31  3:05 ` Darrick J. Wong [this message]
     [not found]   ` <56CED40B.2020304@cn.fujitsu.com>
2016-03-22  1:49     ` Xiaoguang Wang
  -- strict thread matches above, loose matches on Subject: below --
2016-07-12  5:41 Xiao Yang
2016-07-13  4:25 ` Eryu Guan
2016-07-13  5:11   ` Darrick J. Wong
2016-07-13  8:02     ` Xiao Yang
2016-07-14  0:57     ` Xiao Yang
2016-07-14  7:16     ` Guangwen Feng
2016-07-19  2:45   ` 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=20160131030503.GB5849@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=fenggw-fnst@cn.fujitsu.com \
    --cc=fstests@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