From: Ingo Molnar <mingo@elte.hu>
To: Jianjun Kong <jianjun@zeuux.org>
Cc: mingo@redhat.com,
Linux-Kernel-Mailing-List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] x86: fix warning of uninitialized variable
Date: Thu, 4 Dec 2008 11:16:33 +0100 [thread overview]
Message-ID: <20081204101633.GD18708@elte.hu> (raw)
In-Reply-To: <20081204101023.GA18708@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
>
> * Jianjun Kong <jianjun@zeuux.org> wrote:
>
> > fix warning of uninitialized 'base' in arch/x86/kernel/scx200_32.c
> >
> > arch/x86/kernel/scx200_32.c: In function ‘scx200_probe’:
> > arch/x86/kernel/scx200_32.c:82: warning: ‘base’ may be used
> > uninitialized in this function
> >
> > Signed-off-by: Jianjun Kong <jianjun@zeuux.org>
> > ---
> > arch/x86/kernel/scx200_32.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
>
> this patch is wrong, and your analysis-free commit log is wrong as
> well!
>
> i fixed this a few weeks ago, and GCC pinpointed a _real_ bug - which
> you hacked around instead of fixing. See the real fix below.
Also, see an example below of the case where GCC is wrong about a
warning, and how it is annotated.
Ingo
------------->
>From af4d2994e0e8e6e529b0e87f4e436dad062a9c05 Mon Sep 17 00:00:00 2001
From: Ingo Molnar <mingo@elte.hu>
Date: Tue, 25 Nov 2008 13:14:19 +0100
Subject: [PATCH] fix warning in fs/ocfs2/stack_user.c
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
this warning:
fs/ocfs2/stack_user.c: In function ‘user_cluster_connect’:
fs/ocfs2/stack_user.c:807: warning: ‘control’ may be used uninitialized in this function
triggers because GCC does not recognize the (correct) error flow
between:
- ocfs2_live_connection_new() and 'control'
Annotate it.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
fs/ocfs2/stack_user.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/ocfs2/stack_user.c b/fs/ocfs2/stack_user.c
index faec2d8..55e2cdc 100644
--- a/fs/ocfs2/stack_user.c
+++ b/fs/ocfs2/stack_user.c
@@ -804,7 +804,7 @@ static int fs_protocol_compare(struct ocfs2_protocol_version *existing,
static int user_cluster_connect(struct ocfs2_cluster_connection *conn)
{
dlm_lockspace_t *fsdlm;
- struct ocfs2_live_connection *control;
+ struct ocfs2_live_connection *uninitialized_var(control);
int rc = 0;
BUG_ON(conn == NULL);
prev parent reply other threads:[~2008-12-04 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 1:00 [PATCH 1/3] x86: fix warning of uninitialized variable Jianjun Kong
2008-12-04 10:10 ` Ingo Molnar
2008-12-04 10:16 ` Ingo Molnar [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=20081204101633.GD18708@elte.hu \
--to=mingo@elte.hu \
--cc=jianjun@zeuux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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