From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>,
NetFilter <netfilter-devel@vger.kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build warnings after merge of the netfilter-next tree
Date: Mon, 5 Dec 2016 12:19:38 +1100 [thread overview]
Message-ID: <20161205121938.014bc604@canb.auug.org.au> (raw)
Hi all,
After merging the netfilter-next tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from arch/x86/include/asm/checksum.h:4:0,
from include/net/checksum.h:26,
from include/linux/skbuff.h:31,
from include/linux/if_ether.h:23,
from include/uapi/linux/ethtool.h:18,
from include/linux/ethtool.h:17,
from include/linux/netdevice.h:42,
from include/linux/if_vlan.h:15,
from net/netfilter/nft_payload.c:13:
net/netfilter/nft_payload.c: In function 'nft_payload_set_eval':
arch/x86/include/asm/checksum_64.h:184:2: warning: 'tsum' may be used uninitialized in this function [-Wmaybe-uninitialized]
asm("addl %2,%0\n\t"
^
net/netfilter/nft_payload.c:261:15: note: 'tsum' was declared here
__wsum fsum, tsum;
^
In file included from include/linux/skbuff.h:31:0,
from include/linux/if_ether.h:23,
from include/uapi/linux/ethtool.h:18,
from include/linux/ethtool.h:17,
from include/linux/netdevice.h:42,
from include/linux/if_vlan.h:15,
from net/netfilter/nft_payload.c:13:
include/net/checksum.h:71:9: warning: 'fsum' may be used uninitialized in this function [-Wmaybe-uninitialized]
return csum_add(csum, ~addend);
^
net/netfilter/nft_payload.c:261:9: note: 'fsum' was declared here
__wsum fsum, tsum;
^
Introduced by commit
556c291b3a1b ("netfilter: nft_payload: layer 4 checksum adjustment for pseudoheader fields")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-12-05 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 1:19 Stephen Rothwell [this message]
2019-08-14 2:01 linux-next: build warnings after merge of the netfilter-next tree Stephen Rothwell
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=20161205121938.014bc604@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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).