From: Jan Kara <jack@suse.cz>
To: Manish Katiyar <mkatiyar@gmail.com>
Cc: ext4 <linux-ext4@vger.kernel.org>, Theodore Ts'o <tytso@mit.edu>,
cmm@us.ibm.com
Subject: Re: [PATCH] : make sure the buffer head members are zeroed out before using them.
Date: Mon, 26 Jan 2009 14:00:16 +0100 [thread overview]
Message-ID: <20090126130016.GC2726@duck.suse.cz> (raw)
In-Reply-To: <ea11fea30901260448v564b424byc9e4d1bbb289d1d8@mail.gmail.com>
On Mon 26-01-09 18:18:19, Manish Katiyar wrote:
> On Mon, Jan 26, 2009 at 6:03 PM, Manish Katiyar <mkatiyar@gmail.com> wrote:
> > On Mon, Jan 26, 2009 at 5:59 PM, Jan Kara <jack@suse.cz> wrote:
> >>> On Tue, Jan 20, 2009 at 10:36 PM, Manish Katiyar <mkatiyar@gmail.com> wrote:
> >>> > ext2_quota_read doesn't bzeroes tmp_bh before calling ext2_get_block()
> >>> > where we access the b_size of it. Since it is a local variable it
> >>> > might contain some garbage. Make sure it is filled with zero before
> >>> > passing.
> >>>
> >>> Hi Ted/mingming,
> >>>
> >>> Any feedback on this ??
> >> Ops, sorry. I wanted to reply but first I wanted to research more
> >> whether we can set b_size to 0 and then forgot about it. Looking into
> >> other code (e.g. in fs/mpage.c or fs/buffer.c) I think it would be
> >> better to set b_size to sb->s_blocksize and be done with that. Mapping
> >> code does not need anything else set to a deterministic value so using
> >> memset is a bit overkill.
> >
> > Thanks Jan for your comments. Yes memset is an overkill. I did it just
> > because other users of ext2_get_block were doing the same way. Will
> > rework the patch with setting b_size as blocksize and send again.
>
> Here is the updated patch. compile tested.
>
> Signed-off-by : Manish Katiyar <mkatiyar@gmail.com>
Yes, now it looks fine. Thanks for the fix.
Acked-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/ext2/super.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/fs/ext2/super.c b/fs/ext2/super.c
> index da8bdea..2a1c0c6 100644
> --- a/fs/ext2/super.c
> +++ b/fs/ext2/super.c
> @@ -1328,6 +1328,7 @@ static ssize_t ext2_quota_read(struct
> super_block *sb, int type, char *data,
> sb->s_blocksize - offset : toread;
>
> tmp_bh.b_state = 0;
> + tmp_bh.b_size = sb->s_blocksize;
> err = ext2_get_block(inode, blk, &tmp_bh, 0);
> if (err < 0)
> return err;
> @@ -1367,6 +1368,7 @@ static ssize_t ext2_quota_write(struct
> super_block *sb, int type,
> sb->s_blocksize - offset : towrite;
>
> tmp_bh.b_state = 0;
> + tmp_bh.b_size = sb->s_blocksize;
> err = ext2_get_block(inode, blk, &tmp_bh, 1);
> if (err < 0)
> goto out;
> --
> 1.5.4.3
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2009-01-26 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 17:06 [PATCH] : make sure the buffer head members are zeroed out before using them Manish Katiyar
2009-01-25 15:53 ` Manish Katiyar
2009-01-25 16:15 ` Eric Sandeen
2009-01-25 16:22 ` Manish Katiyar
2009-01-25 17:01 ` Eric Sandeen
2009-01-26 12:32 ` Jan Kara
2009-01-26 12:29 ` Jan Kara
2009-01-26 12:33 ` Manish Katiyar
2009-01-26 12:48 ` Manish Katiyar
2009-01-26 13:00 ` Jan Kara [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=20090126130016.GC2726@duck.suse.cz \
--to=jack@suse.cz \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mkatiyar@gmail.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