From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Eric Whitney <enwlinux@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: xfstest failure: #68, with data=journal
Date: Fri, 22 Mar 2013 22:06:28 +0800 [thread overview]
Message-ID: <20130322140628.GA2770@gmail.com> (raw)
In-Reply-To: <20130321221218.GA3349@wallace>
On Thu, Mar 21, 2013 at 06:12:18PM -0400, Eric Whitney wrote:
[snip]
> We were giving this one some attention in late February on the mailing list,
> but I don't think a full solution was found. Here's a pointer to Jan Kara's
> analysis:
>
> http://www.spinics.net/lists/linux-ext4/msg36858.html
>
> Back then, it typically took a number of runs to see this problem.
What I was thinking about this problem is that ext4_file_dio_write() is
missing protection. Look at this link, please [1]. But, after fixing
it, I still can hit a bug. So I believe that more than one bug are
here.
1. http://www.spinics.net/lists/linux-ext4/msg37267.html
Regards,
- Zheng
prev parent reply other threads:[~2013-03-22 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 21:39 xfstest failure: #68, with data=journal Theodore Ts'o
2013-03-21 22:12 ` Eric Whitney
2013-03-22 14:06 ` Zheng Liu [this message]
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=20130322140628.GA2770@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=enwlinux@gmail.com \
--cc=linux-ext4@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.