All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Peter Hurley <peter@hurleysoftware.com>,
	Grant Likely <grant.likely@secretlab.ca>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] tty/serial: Fix uninitialized variable warning
Date: Mon, 04 Mar 2013 10:41:07 +0100	[thread overview]
Message-ID: <51346C33.6080504@suse.cz> (raw)
In-Reply-To: <1362364613.3221.144.camel@thor.lan>

On 03/04/2013 03:36 AM, Peter Hurley wrote:
> On Mon, 2013-03-04 at 09:35 +0800, Grant Likely wrote:
>> drivers/tty/serial/8250/8250.c: In function 'serial_unlink_irq_chain':
>> drivers/tty/serial/8250/8250.c:1676:19: warning: 'i' may be used uninitialized in this function
>>
>> There isn't an actual bug here since the function tests the condition
>> that would cause i to be uninitialized before dereferencing i. However,
>> at least some versions of GCC complain as shown above. (in my case,
>> powerpc gcc 2.5.2). Initializing i to NULL makes it clear to GCC and the
>> casual code reviewer that i will not be dereferenced to a random
>> address.
>>
>> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> ---
>> Greg, some may argue that this is a tool problem, not a kernel problem,
>> but it is useful to me. If anyone objects I'm not going to spend any
>> time championing for this patch.
>>
>> g.
>>
>>  drivers/tty/serial/8250/8250.c |    2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/tty/serial/8250/8250.c b/drivers/tty/serial/8250/8250.c
>> index 0efc815..cbbedcf 100644
>> --- a/drivers/tty/serial/8250/8250.c
>> +++ b/drivers/tty/serial/8250/8250.c
>> @@ -1673,7 +1673,7 @@ static int serial_link_irq_chain(struct uart_8250_port *up)
>>  
>>  static void serial_unlink_irq_chain(struct uart_8250_port *up)
>>  {
>> -	struct irq_info *i;
>> +	struct irq_info *i = NULL;
> 
> struct irq_info *uninitialized_var(i);
> 
> For gcc, the uninitialized_var() #define is in
> include/linux/compiler-gcc.h

As far as I remember, we decided not to use that macro any more after a
bug stemming out of its use.

And Grant uses a very old toolchain as we can see in the commit log. I'm
not sure whether it's worth to hide a potential bug in the future by
this patch.

thanks,
-- 
js
suse labs

  reply	other threads:[~2013-03-04  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  1:35 [PATCH] tty/serial: Fix uninitialized variable warning Grant Likely
2013-03-04  2:36 ` Peter Hurley
2013-03-04  9:41   ` Jiri Slaby [this message]
2013-03-15 20:30 ` Greg Kroah-Hartman
2013-03-15 21:24   ` Grant Likely

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=51346C33.6080504@suse.cz \
    --to=jslaby@suse.cz \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=peter@hurleysoftware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.