From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] libext2fs: write only core inode in update_path()
Date: Wed, 17 Jun 2009 18:00:35 -0500 [thread overview]
Message-ID: <4A397593.8030103@redhat.com> (raw)
In-Reply-To: <20090617225039.GE7867@mit.edu>
Theodore Tso wrote:
> This is what I ultimately checked in. It converts all calls of
> ext2fs_write_inode_full() to ext2fs_write_inode().
Hey thanks for finding those, it fixed the next resize bug I was looking
at! ;)
Now, put down the laptop and pay attention to that talk, Ted ;)
-Eric
> - Ted
>
> commit 125a36780626cdb0fc4d62fd529486baa8bce54c
> Author: Eric Sandeen <sandeen@redhat.com>
> Date: Wed Jun 17 18:49:01 2009 -0400
>
> libext2fs: write only core inode in update_path()
>
> The ext2_extent_handle only has a struct ext2_inode allocated on
> it, and the same amount copied into it in that same function,
> but in update_path() we're possibly writing out more than that -
> for example 256 bytes, from that address. This causes uninitialized
> memory to get written to disk, overwriting the parts of the
> inode past the osd2 member (the end of the smaller structure).
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
>
> diff --git a/lib/ext2fs/extent.c b/lib/ext2fs/extent.c
> index 2b88739..35b080e 100644
> --- a/lib/ext2fs/extent.c
> +++ b/lib/ext2fs/extent.c
> @@ -546,8 +546,8 @@ static errcode_t update_path(ext2_extent_handle_t handle)
> struct ext3_extent_idx *ix;
>
> if (handle->level == 0) {
> - retval = ext2fs_write_inode_full(handle->fs, handle->ino,
> - handle->inode, EXT2_INODE_SIZE(handle->fs->super));
> + retval = ext2fs_write_inode(handle->fs, handle->ino,
> + handle->inode);
> } else {
> ix = handle->path[handle->level - 1].curr;
> blk = ext2fs_le32_to_cpu(ix->ei_leaf) +
> @@ -1011,8 +1011,8 @@ static errcode_t extent_node_split(ext2_extent_handle_t handle)
>
> /* new node hooked in, so update inode block count (do this here?) */
> handle->inode->i_blocks += handle->fs->blocksize / 512;
> - retval = ext2fs_write_inode_full(handle->fs, handle->ino,
> - handle->inode, EXT2_INODE_SIZE(handle->fs->super));
> + retval = ext2fs_write_inode(handle->fs, handle->ino,
> + handle->inode);
> if (retval)
> goto done;
>
> @@ -1370,9 +1370,8 @@ errcode_t ext2fs_extent_delete(ext2_extent_handle_t handle, int flags)
>
> retval = ext2fs_extent_delete(handle, flags);
> handle->inode->i_blocks -= handle->fs->blocksize / 512;
> - retval = ext2fs_write_inode_full(handle->fs,
> - handle->ino, handle->inode,
> - EXT2_INODE_SIZE(handle->fs->super));
> + retval = ext2fs_write_inode(handle->fs, handle->ino,
> + handle->inode);
> ext2fs_block_alloc_stats(handle->fs, extent.e_pblk, -1);
> }
> } else {
next prev parent reply other threads:[~2009-06-17 23:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 22:38 Something wrong with extent-based journal creation Eric Sandeen
2009-06-17 0:57 ` [PATCH] libext2fs: write only core inode in update_path() Eric Sandeen
2009-06-17 15:35 ` Theodore Tso
2009-06-17 15:50 ` Eric Sandeen
2009-06-17 22:50 ` Theodore Tso
2009-06-17 23:00 ` Eric Sandeen [this message]
2009-06-17 8:04 ` Something wrong with extent-based journal creation Andreas Dilger
2009-06-17 14:45 ` Eric Sandeen
2009-06-17 15:31 ` Theodore Tso
-- strict thread matches above, loose matches on Subject: below --
2009-06-17 20:11 [PATCH] libext2fs: write only core inode in update_path() number9652
2009-06-17 20:43 ` Eric Sandeen
2009-06-17 21:32 number9652
2009-06-17 21:36 ` Eric Sandeen
2009-06-17 22:46 ` Theodore Tso
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=4A397593.8030103@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).