From: Manish Katiyar <mkatiyar@gmail.com>
To: ext4 <linux-ext4@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
cmm@us.ibm.com
Cc: mkatiyar@gmail.com
Subject: [PATCH] : make sure the buffer head members are zeroed out before using them.
Date: Tue, 20 Jan 2009 22:36:08 +0530 [thread overview]
Message-ID: <ea11fea30901200906m4dfb5060ya82104519b4984bb@mail.gmail.com> (raw)
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.
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
next reply other threads:[~2009-01-20 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 17:06 Manish Katiyar [this message]
2009-01-25 15:53 ` [PATCH] : make sure the buffer head members are zeroed out before using them 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
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=ea11fea30901200906m4dfb5060ya82104519b4984bb@mail.gmail.com \
--to=mkatiyar@gmail.com \
--cc=cmm@us.ibm.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