Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1266450 > unrolled thread
| Started by | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| First post | 2015-11-10 13:10 +0100 |
| Last post | 2015-11-11 14:20 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
[PATCH] netfilter: nfnetlink_log: work around uninitialized variable warning Arnd Bergmann <arnd@arndb.de> - 2015-11-10 13:10 +0100
Re: [PATCH] netfilter: nfnetlink_log: work around uninitialized variable warning Pablo Neira Ayuso <pablo@netfilter.org> - 2015-11-11 14:20 +0100
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2015-11-10 13:10 +0100 |
| Subject | [PATCH] netfilter: nfnetlink_log: work around uninitialized variable warning |
| Message-ID | <qtfUl-4Tt-5@gated-at.bofh.it> |
After a recent (correct) change, gcc started warning about the use
of the 'flags' variable in nfulnl_recv_config()
net/netfilter/nfnetlink_log.c: In function 'nfulnl_recv_config':
net/netfilter/nfnetlink_log.c:320:14: warning: 'flags' may be used uninitialized in this function [-Wmaybe-uninitialized]
net/netfilter/nfnetlink_log.c:828:6: note: 'flags' was declared here
The warning first shows up in ARM s3c2410_defconfig with gcc-4.3 or
higher (including 5.2.1, which is the latest version I checked) I
tried working around it by rearranging the code but had no success
with that.
As a last resort, this initializes the variable to zero, which shuts
up the warning, but means that we don't get a warning if the code
is ever changed in a way that actually causes the variable to be
used without first being written.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Fixes: 8cbc870829ec ("netfilter: nfnetlink_log: validate dependencies to avoid breaking atomicity")
---
diff --git a/net/netfilter/nfnetlink_log.c b/net/netfilter/nfnetlink_log.c
index 06eb48fceb42..740cce4685ac 100644
--- a/net/netfilter/nfnetlink_log.c
+++ b/net/netfilter/nfnetlink_log.c
@@ -825,7 +825,7 @@ nfulnl_recv_config(struct sock *ctnl, struct sk_buff *skb,
struct net *net = sock_net(ctnl);
struct nfnl_log_net *log = nfnl_log_pernet(net);
int ret = 0;
- u16 flags;
+ u16 flags = 0;
if (nfula[NFULA_CFG_CMD]) {
u_int8_t pf = nfmsg->nfgen_family;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [next] | [standalone]
| From | Pablo Neira Ayuso <pablo@netfilter.org> |
|---|---|
| Date | 2015-11-11 14:20 +0100 |
| Subject | Re: [PATCH] netfilter: nfnetlink_log: work around uninitialized variable warning |
| Message-ID | <qtDtD-3fK-15@gated-at.bofh.it> |
| In reply to | #1266450 |
On Tue, Nov 10, 2015 at 01:08:15PM +0100, Arnd Bergmann wrote: > After a recent (correct) change, gcc started warning about the use > of the 'flags' variable in nfulnl_recv_config() > > net/netfilter/nfnetlink_log.c: In function 'nfulnl_recv_config': > net/netfilter/nfnetlink_log.c:320:14: warning: 'flags' may be used uninitialized in this function [-Wmaybe-uninitialized] > net/netfilter/nfnetlink_log.c:828:6: note: 'flags' was declared here > > The warning first shows up in ARM s3c2410_defconfig with gcc-4.3 or > higher (including 5.2.1, which is the latest version I checked) I > tried working around it by rearranging the code but had no success > with that. > > As a last resort, this initializes the variable to zero, which shuts > up the warning, but means that we don't get a warning if the code > is ever changed in a way that actually causes the variable to be > used without first being written. Applied, thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web