From: Martin Schlemmer <azarah@gentoo.org>
To: chrisl@vmware.com
Cc: KML <linux-kernel@vger.kernel.org>,
akpm@digeo.com, adilger@clusterfs.com, ext3-users@redhat.com,
x86-kernel@gentoo.org,
Ext2 Devel <ext2-devel@lists.sourceforge.net>
Subject: Re: [PATCH] fix for htree corruption. Was: [2.6] Perl weirdness with ext3 and HTREE
Date: Thu, 21 Aug 2003 21:46:06 +0200 [thread overview]
Message-ID: <1061495166.29479.1.camel@nosferatu.lan> (raw)
In-Reply-To: <20030819104026.GA25402@vmware.com>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
On Tue, 2003-08-19 at 12:40, chrisl@vmware.com wrote:
Hi
>
> The first patch should fix it. The bug is trigger by creating the index.
> Coping out the index we assume the dirents start with the first entry
> after "." "..".
>
> It can make the first previous deleted entry reappear.
> In the past we set inode to zero for empty entry so this is not
> a problem. That is not true any more.
>
> Andrew, I assume touch inode->i_ctime after
> ext3_mark_inode_dirty is a bug? The second patch is for that.
>
>
I can confirm that this works as expected, many thanks!
Sorry for the long delay ...
Regards,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-08-21 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 20:22 [2.6] Perl weirdness with ext3 and HTREE Christopher Li
2003-08-06 22:28 ` Martin Schlemmer
2003-08-19 10:40 ` [PATCH] fix for htree corruption. Was: " chrisl
2003-08-19 10:55 ` Andrew Morton
2003-08-19 18:23 ` chrisl
2003-08-19 14:17 ` Martin Schlemmer
2003-08-21 19:46 ` Martin Schlemmer [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=1061495166.29479.1.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=adilger@clusterfs.com \
--cc=akpm@digeo.com \
--cc=chrisl@vmware.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86-kernel@gentoo.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