From: Jan Kara <jack@suse.cz>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
Jan Kara <jack@suse.cz>, Lachlan McIlroy <lmcilroy@redhat.com>
Subject: Re: [PATCH V2] ext3: Always set dx_node's fake_dirent explicitly.
Date: Mon, 7 Mar 2011 17:26:47 +0100 [thread overview]
Message-ID: <20110307162647.GB3663@quack.suse.cz> (raw)
In-Reply-To: <4D7161D8.8010509@redhat.com>
On Fri 04-03-11 16:04:08, Eric Sandeen wrote:
> (crossport of 1f7bebb9e911d870fa8f997ddff838e82b5715ea
> by Andreas Schlick <schlick@lavabit.com>)
>
> When ext3_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: Eric Sandeen <sandeen@redhat.com>
Thanks. Merged - and added CC to stable@kernel.org as Andreas suggested.
> While it's a simple one liner, this took me forever to (re-)find.
I feel with you :).
Honza
>
> diff --git a/fs/ext3/namei.c b/fs/ext3/namei.c
> index b27ba71..75c968e 100644
> --- a/fs/ext3/namei.c
> +++ b/fs/ext3/namei.c
> @@ -1540,8 +1540,8 @@ static int ext3_dx_add_entry(handle_t *handle, struct dentry *dentry,
> goto cleanup;
> node2 = (struct dx_node *)(bh2->b_data);
> entries2 = node2->entries;
> + memset(&node2->fake, 0, sizeof(struct fake_dirent));
> node2->fake.rec_len = ext3_rec_len_to_disk(sb->s_blocksize);
> - node2->fake.inode = 0;
> BUFFER_TRACE(frame->bh, "get_write_access");
> err = ext3_journal_get_write_access(handle, frame->bh);
> if (err)
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2011-03-07 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 22:02 ext3: Always set dx_node's fake_dirent explicitly Eric Sandeen
2011-03-04 22:04 ` [PATCH V2] " Eric Sandeen
2011-03-04 22:23 ` Andreas Dilger
2011-03-07 16:26 ` Jan Kara [this message]
2011-03-07 16:32 ` Eric Sandeen
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=20110307162647.GB3663@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=lmcilroy@redhat.com \
--cc=sandeen@redhat.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).