From: Andrew Morton <akpm@linux-foundation.org>
To: "Theodore Ts'o" <tytso@MIT.EDU>
Cc: linux-kernel@vger.kernel.org, tytso@MIT.EDU, eugene@ibrix.com,
msnitzer@ibrix.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/4] ext3: Fix ext3_dx_readdir hash collision handling
Date: Wed, 17 Sep 2008 12:19:43 -0700 [thread overview]
Message-ID: <20080917121943.904b66b6.akpm@linux-foundation.org> (raw)
In-Reply-To: <1221319971-29879-1-git-send-email-tytso@mit.edu>
On Sat, 13 Sep 2008 11:32:48 -0400
"Theodore Ts'o" <tytso@MIT.EDU> wrote:
> This fixes a bug where readdir() would return a directory entry twice
> if there was a hash collision in an hash tree indexed directory.
That sounds like a serious problem, but given the amount of time it
took to turn up, I guess it's pretty rare.
What are your thoughts regarding a 2.6.27 merge for this? 2.6.26.x?
2.6.25.x? ...
next prev parent reply other threads:[~2008-09-17 19:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 15:32 Theodore Ts'o
2008-09-13 15:32 ` [PATCH 2/4] ext3: truncate block allocated on a failed ext3_write_begin Theodore Ts'o
2008-09-13 15:32 ` [PATCH 3/4] ext2: Avoid printk floods in the face of directory corruption Theodore Ts'o
2008-09-13 15:32 ` [PATCH 4/4] ext3: " Theodore Ts'o
2008-09-18 0:57 ` Eugene Teo
2008-09-17 19:25 ` [PATCH 3/4] ext2: " Andrew Morton
2008-09-17 19:30 ` Eric Sandeen
2008-09-18 9:46 ` Eugene Teo
2008-09-17 19:22 ` [PATCH 2/4] ext3: truncate block allocated on a failed ext3_write_begin Andrew Morton
2008-09-18 7:03 ` Aneesh Kumar K.V
2008-09-17 19:19 ` Andrew Morton [this message]
2008-10-01 22:37 ` [PATCH 1/4] ext3: Fix ext3_dx_readdir hash collision handling Theodore Tso
2008-10-01 23:33 ` Andrew Morton
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=20080917121943.904b66b6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=eugene@ibrix.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msnitzer@ibrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome