From: Eric Sandeen <sandeen@redhat.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
EUNBONG SONG <eunb.song@samsung.com>, Jan Kara <jack@suse.cz>,
"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, Dave Chinner <david@fromorbit.com>
Subject: Re: EXT4 regression caused 4eec7
Date: Mon, 13 May 2013 11:34:12 -0500 [thread overview]
Message-ID: <51911604.2060805@redhat.com> (raw)
In-Reply-To: <87a9o01siw.fsf@openvz.org>
On 5/12/13 4:01 AM, Dmitry Monakhov wrote:
> In fact '4eec70' are vexing because I have reviewed and tested this patch before
> it was marked as Review-by, but missed the bug. This is because xfstests
> was executed manually logs was full of warnings but tainted flag was not
> checked at the end.
Can you elaborate on this? What was logged, and is it something we could
try to pick up post-test in xfstests?
Thanks,
-Eric
next prev parent reply other threads:[~2013-05-13 16:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 0:51 Re: EXT4 panic at jbd2_journal_put_journal_head() in 3.9+ EUNBONG SONG
2013-05-10 0:51 ` EUNBONG SONG
2013-05-10 17:27 ` Tony Luck
2013-05-11 7:52 ` Dmitry Monakhov
2013-05-13 2:04 ` Tony Luck
2013-05-13 3:07 ` Theodore Ts'o
2013-05-13 5:06 ` Sidorov, Andrei
2013-05-13 8:43 ` Zheng Liu
2013-05-10 19:27 ` Theodore Ts'o
2013-05-10 20:38 ` David Daney
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2013-05-12 13:05 Re: " EUNBONG SONG
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
2013-05-13 13:59 ` Dmitry Monakhov
2013-05-13 20:30 ` Theodore Ts'o
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=51911604.2060805@redhat.com \
--to=sandeen@redhat.com \
--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 \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.