From: Pablo Neira Ayuso <pablo@netfilter.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, netfilter-devel@vger.kernel.org,
chamas@h4.dion.ne.jp, chamaken@gmail.com
Subject: Re: [PATCH nf-next v2 2/2] netfilter: rename nfnetlink_queue_core.c to nfnetlink_queue.c
Date: Thu, 1 Oct 2015 14:22:48 +0200 [thread overview]
Message-ID: <20151001122248.GA10264@salvia> (raw)
In-Reply-To: <201510012017.vqRsWNtm%fengguang.wu@intel.com>
On Thu, Oct 01, 2015 at 08:07:45PM +0800, kbuild test robot wrote:
> Hi Pablo,
>
> [auto build test results on next-20151001 -- if it's inappropriate base, please ignore]
>
> config: m68k-sun3_defconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 31ae4524f70d7992a3f918bab674e2fe8588edfa
> # save the attached .config to linux build tree
> make.cross ARCH=m68k
>
> Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
> http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
>
> All warnings (new ones prefixed by >>):
>
> net/netfilter/nfnetlink_queue.c: In function '__nfqnl_enqueue_packet':
> >> net/netfilter/nfnetlink_queue.c:518:18: warning: 'nfq_ct' may be used uninitialized in this function [-Wmaybe-uninitialized]
> if (ct && nfq_ct->build(skb, ct, ctinfo, NFQA_CT, NFQA_CT_INFO) < 0)
> ^
> net/netfilter/nfnetlink_queue.c:316:22: note: 'nfq_ct' was declared here
> struct nfq_ct_hook *nfq_ct;
> ^
JFYI: This is a false positive as the note above states, if ct is set
then nfq_ct is set too.
prev parent reply other threads:[~2015-10-01 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 12:02 [PATCH nf-next v2 1/2] netfilter: nfnetlink_queue: get rid of nfnetlink_queue_ct.c Pablo Neira Ayuso
2015-10-01 12:02 ` [PATCH nf-next v2 2/2] netfilter: rename nfnetlink_queue_core.c to nfnetlink_queue.c Pablo Neira Ayuso
2015-10-01 12:07 ` kbuild test robot
2015-10-01 12:22 ` Pablo Neira Ayuso [this message]
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=20151001122248.GA10264@salvia \
--to=pablo@netfilter.org \
--cc=chamaken@gmail.com \
--cc=chamas@h4.dion.ne.jp \
--cc=kbuild-all@01.org \
--cc=lkp@intel.com \
--cc=netfilter-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.