From: Theodore Tso <tytso@mit.edu>
To: Andreas Schlick <schlick@lavabit.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/2] ext4: Always set dx_node's fake_dirent explicitly.
Date: Thu, 10 Sep 2009 23:19:37 -0400 [thread overview]
Message-ID: <20090911031937.GA20710@mit.edu> (raw)
In-Reply-To: <200908301657.50561.schlick@lavabit.com>
On Sun, Aug 30, 2009 at 04:57:50PM +0200, Andreas Schlick wrote:
> When ext4_dx_add_entry() has to split an index node, it has to ensure that
> name_len of dx_node's fake_dirent is also zero, because otherwise e2fsck
> won't recognise it as an intermediate htree node and consider the htree to
> be corrupted.
>
> Signed-off-by: Andreas Schlick <schlick@lavabit.com>
Added to the ext4 patch queue, thanks.
- Ted
prev parent reply other threads:[~2009-09-11 3:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 14:56 [PATCH 0/2] Fix wrong name_len and file_type in intermediate htree nodes Andreas Schlick
2009-08-30 14:57 ` [PATCH 1/2] ext4: Always set dx_node's fake_dirent explicitly Andreas Schlick
2009-08-30 14:58 ` [PATCH 2/2] ext3: " Andreas Schlick
2009-09-11 3:19 ` Theodore Tso [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=20090911031937.GA20710@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=schlick@lavabit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).