From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [nf-next:nf-nat2 7/8] net/netfilter/nf_nat_ftp.c:122:9: sparse: incorrect type in assignment (differ
Date: Mon, 30 Jul 2012 03:00:27 +0000 [thread overview]
Message-ID: <20120730030027.GB7389@localhost> (raw)
Hi Patrick,
There are new sparse warnings show up in
tree: git://150.214.188.80/nf-next nf-nat2
head: 2c59d9f21ca33d3f974f45ae1f730982a85bd908
commit: 148b7e40adbf42204617d31ea5643f11faba3d33 [7/8] netfilter: nf_nat: support IPv6 in FTP NAT helper
All sparse warnings:
+ net/netfilter/nf_nat_ftp.c:122:9: sparse: incorrect type in assignment (different address spaces)
net/netfilter/nf_nat_ftp.c:122:9: expected unsigned int ( *extern [addressable] [toplevel] nf_nat_ftp_hook )( ... )
net/netfilter/nf_nat_ftp.c:122:9: got void [noderef] <asn:4>*<noident>
+ net/netfilter/nf_nat_ftp.c:129:9: sparse: cannot dereference this type
vim +122 net/netfilter/nf_nat_ftp.c
119
120 static void __exit nf_nat_ftp_fini(void)
121 {
> 122 RCU_INIT_POINTER(nf_nat_ftp_hook, NULL);
123 synchronize_rcu();
124 }
125
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
reply other threads:[~2012-07-30 3:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120730030027.GB7389@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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 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).