From: Eric Sandeen <sandeen@redhat.com>
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: Sun, 25 Jan 2009 10:15:58 -0600 [thread overview]
Message-ID: <497C903E.5080108@redhat.com> (raw)
In-Reply-To: <ea11fea30901250753j6db5158dj9082d57aa9469685@mail.gmail.com>
Manish Katiyar 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 ??
This looks ok to me, Manish. I'm curious, did you see this fail in real
life, and if so, what'd the failure look like?
With the change, the tmp_bh bh_size is 0, so maxblocks down the
get_block path is also 0, but I guess that works out ok.
-Eric
> Thanks -
> Manish
>
>> Signed-off-by : Manish Katiyar <mkatiyar@gmail.com>
>> ---
>> fs/ext2/super.c | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/ext2/super.c b/fs/ext2/super.c
>> index da8bdea..d10aa44 100644
>> --- a/fs/ext2/super.c
>> +++ b/fs/ext2/super.c
>> @@ -1327,7 +1327,7 @@ static ssize_t ext2_quota_read(struct
>> super_block *sb, int type, char *data,
>> tocopy = sb->s_blocksize - offset < toread ?
>> sb->s_blocksize - offset : toread;
>>
>> - tmp_bh.b_state = 0;
>> + memset(&tmp_bh, 0, sizeof(struct buffer_head));
>> err = ext2_get_block(inode, blk, &tmp_bh, 0);
>> if (err < 0)
>> return err;
>> @@ -1366,7 +1366,7 @@ static ssize_t ext2_quota_write(struct
>> super_block *sb, int type,
>> tocopy = sb->s_blocksize - offset < towrite ?
>> sb->s_blocksize - offset : towrite;
>>
>> - tmp_bh.b_state = 0;
>> + memset(&tmp_bh, 0, sizeof(struct buffer_head));
>> err = ext2_get_block(inode, blk, &tmp_bh, 1);
>> if (err < 0)
>> goto out;
>> --
>> 1.5.4.3
>>
>>
>> Thanks -
>> Manish
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-25 16:16 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 [this message]
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
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=497C903E.5080108@redhat.com \
--to=sandeen@redhat.com \
--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