[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53050ED0.40108@suse.cz>
Date: Wed, 19 Feb 2014 21:06:40 +0100
From: Jiri Slaby <jslaby@...e.cz>
To: Paul Gortmaker <paul.gortmaker@...driver.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
Alan Cox <alan@...ux.intel.com>
Subject: Re: [PATCH] drivers/tty/serial: deal with 8250_core.c uninitialized
warning for good
On 02/19/2014 09:00 PM, Paul Gortmaker wrote:
> Every couple of months, someone sends a patch to fix:
>
> drivers/tty/serial/8250/8250_core.c: In function 'serial_unlink_irq_chain':
> drivers/tty/serial/8250/8250_core.c:1712:2: warning: 'i' may be used uninitialized in this function [-Wuninitialized]
>
> and they in turn get a NACK for their efforts, and are told that
> their compiler is broken. This has been going on since at least
> the year 2008: https://lkml.org/lkml/2008/11/24/433
>
> Lets add a comment, so that subsequent patches don't get as far as
> the maintainers or the mailing lists.
Hi, wouldn't hlist_for_each_entry do a better job to silent both the
compiler and the reporters with the added value of cleanup?
> Cc: Alan Cox <alan@...ux.intel.com>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@...driver.com>
>
> diff --git a/drivers/tty/serial/8250/8250_core.c b/drivers/tty/serial/8250/8250_core.c
> index 69932b7556cf..747073b8c38a 100644
> --- a/drivers/tty/serial/8250/8250_core.c
> +++ b/drivers/tty/serial/8250/8250_core.c
> @@ -1694,6 +1694,10 @@ static int serial_link_irq_chain(struct uart_8250_port *up)
>
> static void serial_unlink_irq_chain(struct uart_8250_port *up)
> {
> + /*
> + * yes, some broken gcc emit "warning: 'i' may be used uninitialized"
> + * but no, we are not going to take a patch that assigns NULL below.
> + */
> struct irq_info *i;
> struct hlist_node *n;
> struct hlist_head *h;
thanks,
--
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists