From: Eric Sandeen <sandeen@redhat.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH] ext4: ext4_mb_initialize_context() forgets to initialize some fields
Date: Fri, 10 Jul 2009 15:59:06 -0500 [thread overview]
Message-ID: <4A57AB9A.4050208@redhat.com> (raw)
In-Reply-To: <20090710204754.18406.15771.stgit@mj.roinet.com>
Pavel Roskin wrote:
> kmemcheck indicates that ext4_mb_store_histroy() accesses uninitialized
> values of ac->ac_tail and ac->ac_buddy.
>
> Signed-off-by: Pavel Roskin <proski@gnu.org>
> ---
> fs/ext4/mballoc.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 519a0a6..a5a9a35 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -4223,6 +4223,8 @@ ext4_mb_initialize_context(struct ext4_allocation_context *ac,
> ac->ac_groups_scanned = 0;
> ac->ac_ex_scanned = 0;
> ac->ac_found = 0;
> + ac->ac_tail = 0;
> + ac->ac_buddy = 0;
> ac->ac_sb = sb;
> ac->ac_inode = ar->inode;
> ac->ac_o_ex.fe_logical = ar->logical;
Looks good to me; I think it's harmless in the end because we just wind
up w/ garbage in the history if anyone looks, but much better to not
have garbage! :)
At this point I think we are initializing almost all of the 22
allocation context members and 16 of those are 0/NULL; perhaps it'd be
simpler and/or more efficient to just start with a memset(0), but either
way.
(side note, looks like ac_repeats is completely unused...)
Thanks,
-Eric
next prev parent reply other threads:[~2009-07-10 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 20:47 [PATCH] ext4: ext4_mb_initialize_context() forgets to initialize some fields Pavel Roskin
2009-07-10 20:59 ` Eric Sandeen [this message]
2009-07-13 13:46 ` Theodore Tso
2009-07-13 21:27 ` Pavel Roskin
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=4A57AB9A.4050208@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=proski@gnu.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).