From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [2.6 patch] fs/gfs2/dir.c:gfs2_dir_write_data(): don't use an uninitialized variable
Date: Thu, 19 Oct 2006 14:36:21 +0100 [thread overview]
Message-ID: <1161264981.27980.142.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <20061019132003.GN3502@stusta.de>
Hi,
All three patches are now in the GFS2 git tree. Thanks,
Steve.
On Thu, 2006-10-19 at 15:20 +0200, Adrian Bunk wrote:
> In the "if (extlen)" case, "new" might be used uninitialized.
>
> Looking at the code, it should be initialized to 0.
>
> Spotted by the Coverity checker.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> --- linux-2.6/fs/gfs2/dir.c.old 2006-10-19 01:08:00.000000000 +0200
> +++ linux-2.6/fs/gfs2/dir.c 2006-10-19 01:08:18.000000000 +0200
> @@ -169,37 +169,37 @@ static int gfs2_dir_write_data(struct gf
> return gfs2_dir_write_stuffed(ip, buf, (unsigned int)offset,
> size);
>
> if (gfs2_assert_warn(sdp, gfs2_is_jdata(ip)))
> return -EINVAL;
>
> if (gfs2_is_stuffed(ip)) {
> error = gfs2_unstuff_dinode(ip, NULL);
> if (error)
> return error;
> }
>
> lblock = offset;
> o = do_div(lblock, sdp->sd_jbsize) + sizeof(struct gfs2_meta_header);
>
> while (copied < size) {
> unsigned int amount;
> struct buffer_head *bh;
> - int new;
> + int new = 0;
>
> amount = size - copied;
> if (amount > sdp->sd_sb.sb_bsize - o)
> amount = sdp->sd_sb.sb_bsize - o;
>
> if (!extlen) {
> new = 1;
> error = gfs2_extent_map(&ip->i_inode, lblock, &new,
> &dblock, &extlen);
> if (error)
> goto fail;
> error = -EIO;
> if (gfs2_assert_withdraw(sdp, dblock))
> goto fail;
> }
>
> if (amount == sdp->sd_jbsize || new)
> error = gfs2_dir_get_new_buffer(ip, dblock, &bh);
>
prev parent reply other threads:[~2006-10-19 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 13:20 [Cluster-devel] [2.6 patch] fs/gfs2/dir.c:gfs2_dir_write_data(): don't use an uninitialized variable Adrian Bunk
2006-10-19 13:36 ` Steven Whitehouse [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=1161264981.27980.142.camel@quoit.chygwyn.com \
--to=swhiteho@redhat.com \
/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).