From: Christian Hesse <mail@eworm.de>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Oops with ext4 from 2.6.27-rc3
Date: Wed, 13 Aug 2008 23:07:06 +0200 [thread overview]
Message-ID: <200808132307.07437.mail@eworm.de> (raw)
In-Reply-To: <20080813210408.GC6142@mit.edu>
On Wednesday 13 August 2008, Theodore Tso wrote:
> On Wed, Aug 13, 2008 at 10:55:07PM +0200, Christian Hesse wrote:
> > > Can you reproduce the bug?
> >
> > I can. ;)
>
> Great! I haven't been able to reproduce it myself, but I was using a
> very quick test case on small toy filesystem. My ext4 root filesystem
> is 100% extent based files --- and this bug is only happening on
> old-style files with indirect-block-style inodes. And I'm trying to
> get things done before leaving for a family reunion on Friday, so I
> just don't have the time to set up a reproducer.
>
> Can you verify whether or not my patch fixes things for you?
Please look at the bottom of my last two mails... That was with your patch
applied.
--
Regards,
Chris
next prev parent reply other threads:[~2008-08-13 21:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 18:28 Oops with ext4 from 2.6.27-rc3 eworm
2008-08-13 20:10 ` Theodore Tso
2008-08-13 20:55 ` Christian Hesse
2008-08-13 21:04 ` Theodore Tso
2008-08-13 21:07 ` Christian Hesse [this message]
2008-08-13 22:01 ` Theodore Tso
2008-08-13 22:19 ` Eric Sandeen
2008-08-13 22:45 ` Theodore Tso
2008-08-14 4:12 ` Rishikesh K Rajak
2008-08-14 0:10 ` Mingming Cao
2008-08-14 1:51 ` Theodore Tso
2008-08-14 6:59 ` Christian Hesse
2008-08-14 14:58 ` Mingming Cao
2008-08-14 17:52 ` Aneesh Kumar K.V
[not found] ` <216e58580808132159y53fc5403xb52839e1be2186a6@mail.gmail.com>
2008-08-14 5:39 ` Rishikesh K Rajak
2008-08-14 6:13 ` Christian Hesse
2008-08-14 6:16 ` Rishikesh K Rajak
-- strict thread matches above, loose matches on Subject: below --
2008-08-13 21:03 Christian Hesse
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=200808132307.07437.mail@eworm.de \
--to=mail@eworm.de \
--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.