From: Theodore Ts'o <tytso@mit.edu>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: Jan Kara <jack@suse.cz>, EUNBONG SONG <eunb.song@samsung.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>
Subject: Re: EXT4 regression caused 4eec7
Date: Mon, 13 May 2013 09:52:21 -0400 [thread overview]
Message-ID: <20130513135221.GE4845@thunk.org> (raw)
In-Reply-To: <87bo8fxa92.fsf@openvz.org>
On Mon, May 13, 2013 at 05:47:05PM +0400, Dmitry Monakhov wrote:
> In fact generic/299 always succeed for me, but it produce warning
> WARNING: at fs/ext4/inode.c:3218 ext4_ext_direct_IO
> and complains from slab debug. But it was missed because i've missed
> this error in the logs and forget to check /proc/sys/kernel/tained.
This is how it's failing for me....
generic/299 [23:06:27][ 109.243220] fio (3376) used greatest stack depth: 5240 bytes left
[ 109.252757] fio (3380) used greatest stack depth: 5140 bytes left
[ 109.307227] fio (3374) used greatest stack depth: 4944 bytes left
[23:08:10] [failed, exit status 1] - output mismatch (see /root/xfstests/results/generic/299.out.bad)
--- tests/generic/299.out 2013-04-05 21:41:17.000000000 -0400
+++ /root/xfstests/results/generic/299.out.bad 2013-05-11 23:08:10.835356876 -0400
@@ -3,3 +3,6 @@
Run fio with random aio-dio pattern
Start fallocate/truncate loop
+./common/rc: line 2055: 3335 Segmentation fault "$@" >> $seqres.full 2>&1
+failed: '/root/xfstests/bin/fio /tmp/3135-299.fio'
+(see /root/xfstests/results/generic/299.full for details)
...
(Run 'diff -u tests/generic/299.out /root/xfstests/results/generic/299.out.bad' to see the entire diff)
I haven't had a chance to investigate the core dump yet....
- Ted
next prev parent reply other threads:[~2013-05-13 13:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 13:05 Re: Re: EXT4 regression caused 4eec7 EUNBONG SONG
2013-05-12 13:40 ` Dmitry Monakhov
2013-05-13 13:18 ` Jan Kara
2013-05-13 13:30 ` Theodore Ts'o
2013-05-13 13:38 ` Jan Kara
2013-05-13 13:47 ` Dmitry Monakhov
2013-05-13 13:52 ` Theodore Ts'o [this message]
2013-05-13 13:59 ` Dmitry Monakhov
2013-05-13 20:30 ` Theodore Ts'o
2013-05-13 13:56 ` Re: " Zheng Liu
2013-05-13 15:17 ` Jan Kara
2013-05-13 16:43 ` Zheng Liu
-- strict thread matches above, loose matches on Subject: below --
2013-05-10 0:51 Re: EXT4 panic at jbd2_journal_put_journal_head() in 3.9+ EUNBONG SONG
2013-05-10 19:27 ` Theodore Ts'o
2013-05-11 8:13 ` Nasty memory corrution v3.9-12555-g2dbd3ca Dmitry Monakhov
2013-05-11 9:17 ` Dmitry Monakhov
2013-05-11 11:00 ` EXT4 regression caused 4eec7 Dmitry Monakhov
2013-05-11 23:05 ` Theodore Ts'o
2013-05-12 9:01 ` Dmitry Monakhov
2013-05-13 16:34 ` Eric Sandeen
2013-05-13 17:01 ` Jan Kara
2013-05-13 17:09 ` Eric Sandeen
2013-05-14 7:11 ` Dmitry Monakhov
2013-05-14 14:08 ` Eric Sandeen
2013-05-14 22:04 ` Jan Kara
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=20130513135221.GE4845@thunk.org \
--to=tytso@mit.edu \
--cc=david@fromorbit.com \
--cc=dmonakhov@openvz.org \
--cc=eunb.song@samsung.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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).