From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Theodore Ts'o <tytso@mit.edu>, Dave Jones <davej@redhat.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: torrent hash failures since 3.9.0-rc1
Date: Tue, 12 Mar 2013 07:16:24 +0100 [thread overview]
Message-ID: <20130312061624.GA436@x4> (raw)
In-Reply-To: <20130312033054.GB18595@thunk.org>
On 2013.03.11 at 23:30 -0400, Theodore Ts'o wrote:
> On Tue, Mar 12, 2013 at 11:00:58AM +0800, Zheng Liu wrote:
> >
> > Thanks for reporting this problem. My deepest apologies.
> >
> > As Ted suggested, could you please try to use ext4 git tree? I want to
> > make sure whether this bug has been fixed by my lastest patch series or
> > not.
>
> It's definitely worth a try to compile the master branch of the ext4
> tree and see if it reproduces or not.
I cannot reproduce the issue on top of "ext4.git dev", so fortunately
the problem seems to be already fixed there.
Thanks.
Do you guys have a hunch which commit is the actual fix?
(Maybe I will "bisect" it later today.)
--
Markus
next prev parent reply other threads:[~2013-03-12 6:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 17:18 torrent hash failures since 3.9.0-rc1 Markus Trippelsdorf
2013-03-11 19:17 ` Markus Trippelsdorf
2013-03-11 19:41 ` Dave Jones
2013-03-11 20:13 ` Markus Trippelsdorf
2013-03-11 20:37 ` Theodore Ts'o
2013-03-11 20:46 ` Markus Trippelsdorf
2013-03-11 21:18 ` Theodore Ts'o
2013-03-11 21:38 ` Markus Trippelsdorf
2013-03-11 23:12 ` Markus Trippelsdorf
2013-03-11 23:26 ` Dave Jones
2013-03-12 3:00 ` Zheng Liu
2013-03-12 3:30 ` Theodore Ts'o
2013-03-12 3:44 ` Theodore Ts'o
2013-03-12 6:16 ` Markus Trippelsdorf [this message]
2013-03-12 6:44 ` Zheng Liu
2013-03-12 6:48 ` Markus Trippelsdorf
2013-03-12 7:16 ` Zheng Liu
2013-03-12 13:28 ` Theodore Ts'o
2013-03-13 10:15 ` Zheng Liu
2013-03-12 8:28 ` Sander
2013-03-12 22:04 ` Dave Chinner
2013-03-11 20:44 ` Dave Jones
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=20130312061624.GA436@x4 \
--to=markus@trippelsdorf.de \
--cc=davej@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wenqing.lz@taobao.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 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.