From: kbuild test robot <lkp@intel.com>
To: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org
Subject: [net-next:master 408/425] net/rds/connection.c:71:31: sparse: incorrect type in argument 1 (different base types)
Date: Thu, 2 Aug 2018 05:16:27 +0800 [thread overview]
Message-ID: <201808020524.t0cGTgrI%fengguang.wu@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head: b69ab96ab13ddaa28a506a2433ae5b12669615e8
commit: e65d4d96334e3ff4fe0064612a93a51c63de08de [408/425] rds: Remove IPv6 dependency
reproduce:
# apt-get install sparse
git checkout e65d4d96334e3ff4fe0064612a93a51c63de08de
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> net/rds/connection.c:71:31: sparse: incorrect type in argument 1 (different base types) @@ expected restricted __be32 const [usertype] laddr @@ got unsigned inrestricted __be32 const [usertype] laddr @@
net/rds/connection.c:71:31: expected restricted __be32 const [usertype] laddr
net/rds/connection.c:71:31: got unsigned int [unsigned] [assigned] [usertype] lhash
>> net/rds/connection.c:71:41: sparse: incorrect type in argument 3 (different base types) @@ expected restricted __be32 const [usertype] faddr @@ got unsigned inrestricted __be32 const [usertype] faddr @@
net/rds/connection.c:71:41: expected restricted __be32 const [usertype] faddr
net/rds/connection.c:71:41: got unsigned int [unsigned] [assigned] [usertype] fhash
include/linux/slab.h:631:13: sparse: undefined identifier '__builtin_mul_overflow'
include/linux/slab.h:631:13: sparse: call with no type!
vim +71 net/rds/connection.c
53
54 static struct hlist_head *rds_conn_bucket(const struct in6_addr *laddr,
55 const struct in6_addr *faddr)
56 {
57 static u32 rds6_hash_secret __read_mostly;
58 static u32 rds_hash_secret __read_mostly;
59
60 u32 lhash, fhash, hash;
61
62 net_get_random_once(&rds_hash_secret, sizeof(rds_hash_secret));
63 net_get_random_once(&rds6_hash_secret, sizeof(rds6_hash_secret));
64
65 lhash = (__force u32)laddr->s6_addr32[3];
66 #if IS_ENABLED(CONFIG_IPV6)
67 fhash = __ipv6_addr_jhash(faddr, rds6_hash_secret);
68 #else
69 fhash = (__force u32)faddr->s6_addr32[3];
70 #endif
> 71 hash = __inet_ehashfn(lhash, 0, fhash, 0, rds_hash_secret);
72
73 return &rds_conn_hash[hash & RDS_CONNECTION_HASH_MASK];
74 }
75
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
reply other threads:[~2018-08-01 23:04 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=201808020524.t0cGTgrI%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ka-cheong.poon@oracle.com \
--cc=kbuild-all@01.org \
--cc=netdev@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