From: Eric Sandeen <sandeen@sandeen.net>
To: CAI Qian <caiqian@redhat.com>
Cc: linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)
Date: Fri, 31 May 2013 00:35:08 -0500 [thread overview]
Message-ID: <51A8368C.8090006@sandeen.net> (raw)
In-Reply-To: <1462663454.9294499.1369969415681.JavaMail.root@redhat.com>
On 5/30/13 10:03 PM, CAI Qian wrote:
> OK, so the minimal workload to trigger this I found so far was to
> run trinity, ltp and then xfstests. I have been able to easily
> reproduced on 3 servers so far, and I'll post full logs here for
> LKML and linux-mm as this may unrelated to XFS only. As far as
> I can tell from the previous testing results, this has never been
> reproduced back in 3.9 GA time. This seems also been reproduced
> on 3.10-rc3 mostly on s390x so far.
> CAI Qian
>
Can you hit it w/o trinity? I ask because trinity's stated
goal is to fuzz and corrupt, right - so it's quite possible
that blowing up later in xfs is a side effect?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-31 5:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <510292845.4997401.1369279175460.JavaMail.root@redhat.com>
2013-05-23 3:21 ` 3.9.3: Oops running xfstests CAI Qian
2013-05-23 3:51 ` Dave Chinner
2013-05-24 8:52 ` CAI Qian
2013-05-27 5:36 ` Dave Chinner
2013-05-27 6:04 ` CAI Qian
2013-05-28 4:31 ` CAI Qian
2013-05-30 3:45 ` CAI Qian
2013-05-30 5:20 ` Dave Chinner
2013-05-30 5:40 ` CAI Qian
2013-05-31 3:03 ` 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests) CAI Qian
2013-05-31 5:35 ` Eric Sandeen [this message]
2013-05-31 6:04 ` Dave Chinner
2013-06-03 3:04 ` CAI Qian
2013-06-03 4:00 ` Dave Chinner
2013-06-04 3:14 ` CAI Qian
2013-06-04 4:16 ` Dave Chinner
2013-06-04 4:29 ` Dave Chinner
2013-06-04 4:57 ` CAI Qian
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=51A8368C.8090006@sandeen.net \
--to=sandeen@sandeen.net \
--cc=caiqian@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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