LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jiri Kosina <jikos@jikos.cz>
To: Lee Revell <rlrevell@joe-job.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
andrea@suse.de, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: fs/block_dev.c:953: warning: 'found' might be used uninitialized in this function
Date: Wed, 28 Mar 2007 19:23:32 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0703281909240.29565@twin.jikos.cz> (raw)
In-Reply-To: <75b66ecd0703280956i522cf6cbyc4c9ef8b1666ec15@mail.gmail.com>
On Wed, 28 Mar 2007, Lee Revell wrote:
> > I compiled current git source 2.6.21-rc5-g28defbe and got this warning:
> > ...
> > fs/block_dev.c: In function `bd_claim_by_kobject':
> > fs/block_dev.c:953: warning: 'found' might be used uninitialized in this
> > function
> > ...
> Most of these warnings are really GCC bugs. Please examine the code
> in question.
Anyway imho this time gcc got it right?
From: Jiri Kosina <jkosina@suse.cz>
blockdev: bd_claim_by_kobject() could check value of unititalized pointer
Fixes this warning:
fs/block_dev.c: In function `bd_claim_by_kobject':
fs/block_dev.c:953: warning: 'found' might be used uninitialized in this function
struct bd_holder *found is initialized only when bd_claim() returns zero. If it
returns nonzero, ptr stays uninitialized. Later the value of the pointer is checked.
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
diff --git a/drivers/usb/input/hid-tmff.c b/drivers/usb/input/hid-tmff.c
diff --git a/fs/block_dev.c b/fs/block_dev.c
index 575076c..e87d84a 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -950,7 +950,7 @@ static int bd_claim_by_kobject(struct block_device *bdev, void *holder,
struct kobject *kobj)
{
int res;
- struct bd_holder *bo, *found;
+ struct bd_holder *bo, *found = NULL;
if (!kobj)
return -EINVAL;
next prev parent reply other threads:[~2007-03-28 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 16:47 Toralf Förster
2007-03-28 16:56 ` Lee Revell
2007-03-28 17:23 ` Jiri Kosina [this message]
2007-03-28 20:14 ` Andrew Morton
2007-03-28 21:59 ` Dan Aloni
2007-03-30 3:16 ` Kyle Moffett
2007-03-30 19:47 ` Adrian Bunk
2007-03-31 3:09 ` Cong WANG
2007-03-31 8:11 ` Toralf Förster
2007-03-31 14:04 ` Adrian Bunk
2007-03-30 19:40 ` Adrian Bunk
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=Pine.LNX.4.64.0703281909240.29565@twin.jikos.cz \
--to=jikos@jikos.cz \
--cc=akpm@linux-foundation.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=toralf.foerster@gmx.de \
--cc=viro@zeniv.linux.org.uk \
--subject='Re: fs/block_dev.c:953: warning: '\''found'\'' might be used uninitialized in this function' \
/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
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).