From: Paul P Komkoff Jr <i@stingr.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
ext2-devel@lists.sourceforge.net
Subject: Re: problems with ext3 fs, kernels up to 2.6.6-rc2
Date: Thu, 20 May 2004 10:40:51 +0400 [thread overview]
Message-ID: <20040520064051.GP19183@stingr.net> (raw)
In-Reply-To: <20040519170604.GS18086@schnapps.adilger.int>
Replying to Andreas Dilger:
> This seems to fix the majority of the problems, although there are still
> some rare failures in the rename test.
Just curious. Is it really doing what it should? Is there are cases
where ext3_delete_entry(handle, old_dir, old_de, old_bh) will be
called twice with the same set of parameters? :()
--
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
This message represents the official view of the voices in my head
next prev parent reply other threads:[~2004-05-20 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 10:41 problems with ext3 fs, kernels up to 2.6.6-rc2 Paul P Komkoff Jr
2004-05-19 17:06 ` Andreas Dilger
2004-05-20 6:40 ` Paul P Komkoff Jr [this message]
2004-05-20 9:22 ` [Ext2-devel] " Andreas Dilger
2004-05-25 16:58 ` Andreas Dilger
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=20040520064051.GP19183@stingr.net \
--to=i@stingr.net \
--cc=akpm@osdl.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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