From: Fengguang Wu <fengguang.wu@intel.com>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
lkp@01.org, linux-fsdevel@vger.kernel.org
Subject: Re: [aio] e52ddd946a: xfstests generic/211 fail
Date: Sun, 23 Mar 2014 08:58:33 +0800 [thread overview]
Message-ID: <20140323005833.GA14807@localhost> (raw)
In-Reply-To: <20140323005730.GA14629@localhost>
On Sun, Mar 23, 2014 at 08:57:30AM +0800, Fengguang Wu wrote:
> On Sat, Mar 22, 2014 at 08:51:05PM -0400, Benjamin LaHaise wrote:
> > On Sun, Mar 23, 2014 at 08:40:09AM +0800, Fengguang Wu wrote:
> > > Hi Benjamin,
> > >
> > > We noticed xfstests fail and the first bad commit is
> >
> > What is the failure? This is awfully vague for a bug report.
>
> In the email title: the generic/211 case of xfstests.
>
> Here are the rough steps to reproduce the problem in KVM:
>
> mkfs -t ext4 -q /dev/vda
> mkfs -t ext4 -q /dev/vdd
> mount -t ext4 /dev/vda /fs/vda
> mount -t ext4 /dev/vdd /fs/vdd
> export TEST_DIR=/fs/vda
> export TEST_DEV=/dev/vda
> export SCRATCH_DEV=/dev/vdd
> export SCRATCH_MNT=/fs/scratch
> mkdir /fs/scratch -p
> ./check generic/211
generic/211 [failed, exit status 1] - output mismatch (see /lkp/benchmarks/xfstests/results//generic/211.out.bad)
--- tests/generic/211.out 2013-09-16 21:19:49.000000000 +0800
+++ /lkp/benchmarks/xfstests/results//generic/211.out.bad 2014-03-23 02:55:53.390625000 +0800
@@ -1,2 +1,2 @@
QA output created by 211
-aio-free-ring-with-bogus-nr-pages: Success!
+aio-free-ring-with-bogus-nr-pages: Error: io_setup returned -11, expected -ENOMEM
...
(Run 'diff -u tests/generic/211.out /lkp/benchmarks/xfstests/results//generic/211.out.bad' to see the entire diff)
next prev parent reply other threads:[~2014-03-23 0:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140323004009.GA13869@localhost>
[not found] ` <20140323005105.GB4173@kvack.org>
2014-03-23 0:57 ` [aio] e52ddd946a: xfstests generic/211 fail Fengguang Wu
2014-03-23 0:58 ` Fengguang Wu [this message]
2014-03-23 1:03 ` Benjamin LaHaise
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=20140323005833.GA14807@localhost \
--to=fengguang.wu@intel.com \
--cc=bcrl@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.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).