netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: David Howells <dhowells@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	clang-built-linux@googlegroups.com,
	Nick Desaulniers <ndesaulniers@google.com>,
	YueHaibing <yuehaibing@huawei.com>,
	linux-afs@lists.infradead.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rxrpc: avoid clang -Wuninitialized warning
Date: Fri, 22 Mar 2019 08:22:09 -0700	[thread overview]
Message-ID: <20190322152209.GC13220@archlinux-ryzen> (raw)
In-Reply-To: <20190322141848.659387-1-arnd@arndb.de>

On Fri, Mar 22, 2019 at 03:18:43PM +0100, Arnd Bergmann wrote:
> clang produces a false-positive warning as it fails to notice
> that "lost = true" implies that "ret" is initialized:
> 
> net/rxrpc/output.c:402:6: error: variable 'ret' is used uninitialized whenever 'if' condition is true [-Werror,-Wsometimes-uninitialized]
>         if (lost)
>             ^~~~
> net/rxrpc/output.c:437:6: note: uninitialized use occurs here
>         if (ret >= 0) {
>             ^~~
> net/rxrpc/output.c:402:2: note: remove the 'if' if its condition is always false
>         if (lost)
>         ^~~~~~~~~
> net/rxrpc/output.c:339:9: note: initialize the variable 'ret' to silence this warning
>         int ret, opt;
>                ^
>                 = 0
> 
> Rearrange the code to make that more obvious and avoid the warning.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Reviewed-by: Nathan Chancellor <natechancellor@gmail.com>

> ---
>  net/rxrpc/output.c | 11 +++++------
>  1 file changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/net/rxrpc/output.c b/net/rxrpc/output.c
> index 736aa9281100..004c762c2e8d 100644
> --- a/net/rxrpc/output.c
> +++ b/net/rxrpc/output.c
> @@ -335,7 +335,6 @@ int rxrpc_send_data_packet(struct rxrpc_call *call, struct sk_buff *skb,
>  	struct kvec iov[2];
>  	rxrpc_serial_t serial;
>  	size_t len;
> -	bool lost = false;
>  	int ret, opt;
>  
>  	_enter(",{%d}", skb->len);
> @@ -393,14 +392,14 @@ int rxrpc_send_data_packet(struct rxrpc_call *call, struct sk_buff *skb,
>  		static int lose;
>  		if ((lose++ & 7) == 7) {
>  			ret = 0;
> -			lost = true;
> +			trace_rxrpc_tx_data(call, sp->hdr.seq, serial,
> +					    whdr.flags, retrans, true);
> +			goto done;
>  		}
>  	}
>  
> -	trace_rxrpc_tx_data(call, sp->hdr.seq, serial, whdr.flags,
> -			    retrans, lost);
> -	if (lost)
> -		goto done;
> +	trace_rxrpc_tx_data(call, sp->hdr.seq, serial, whdr.flags, retrans,
> +			    false);
>  
>  	/* send the packet with the don't fragment bit set if we currently
>  	 * think it's small enough */
> -- 
> 2.20.0
> 

  reply	other threads:[~2019-03-22 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 14:18 [PATCH] rxrpc: avoid clang -Wuninitialized warning Arnd Bergmann
2019-03-22 15:22 ` Nathan Chancellor [this message]
2019-03-24  1:49 ` David Miller

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=20190322152209.GC13220@archlinux-ryzen \
    --to=natechancellor@gmail.com \
    --cc=arnd@arndb.de \
    --cc=clang-built-linux@googlegroups.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=yuehaibing@huawei.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).