[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161108231313.GA6329@salvia>
Date: Wed, 9 Nov 2016 00:13:13 +0100
From: Pablo Neira Ayuso <pablo@...filter.org>
To: Shuah Khan <shuahkh@....samsung.com>
Cc: kaber@...sh.net, kadlec@...ckhole.kfki.hu, davem@...emloft.net,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net/netfilter: Fix use uninitialized warn in
nft_range_eval()
On Mon, Nov 07, 2016 at 08:41:14AM -0700, Shuah Khan wrote:
> Fix the following warn:
>
> CC [M] net/netfilter/nft_range.o
> 8601,8605c9105
> net/netfilter/nft_range.c: In function ‘nft_range_eval’:
> net/netfilter/nft_range.c:45:5: warning: ‘mismatch’ may be used uninitialized in this function [-Wmaybe-uninitialized]
> if (mismatch)
> ^
You probably using an old tree snapshot? This was already fixed by:
commit d2e4d593516e877f1f6fb40031eb495f36606e16
Author: Arnd Bergmann <arnd@...db.de>
Date: Tue Oct 18 00:05:30 2016 +0200
netfilter: nf_tables: avoid uninitialized variable warning
The newly added nft_range_eval() function handles the two possible
nft range operations, but as the compiler warning points out,
any unexpected value would lead to the 'mismatch' variable being
used without being initialized:
Powered by blists - more mailing lists