From: kbuild test robot <lkp@intel.com>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: kbuild-all@01.org, davem@davemloft.net, netdev@vger.kernel.org,
dsa@cumulusnetworks.com, nikolay@cumulusnetworks.com,
idosch@mellanox.com
Subject: Re: [PATCH net-next v2 2/3] ipv6: support sport and dport in RTM_GETROUTE
Date: Mon, 7 May 2018 14:23:06 +0800 [thread overview]
Message-ID: <201805071454.M3MseL9U%fengguang.wu@intel.com> (raw)
In-Reply-To: <1525654787-21990-3-git-send-email-roopa@cumulusnetworks.com>
Hi Roopa,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Roopa-Prabhu/fib-rule-selftest/20180507-094538
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
net/ipv6/route.c:2591:15: sparse: expression using sizeof(void)
net/ipv6/route.c:1391:15: sparse: expression using sizeof(void)
net/ipv6/route.c:1590:36: sparse: incorrect type in initializer (different address spaces) @@ expected struct fib6_info *from @@ got struct fib6_info struct fib6_info *from @@
net/ipv6/route.c:1590:36: expected struct fib6_info *from
net/ipv6/route.c:1590:36: got struct fib6_info [noderef] <asn:4>*from
net/ipv6/route.c:1968:39: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [unsigned] [usertype] flow_label @@ got gned] [usertype] flow_label @@
net/ipv6/route.c:1968:39: expected unsigned int [unsigned] [usertype] flow_label
net/ipv6/route.c:1968:39: got restricted __be32
net/ipv6/route.c:2311:15: sparse: expression using sizeof(void)
>> net/ipv6/route.c:4735:29: sparse: incorrect type in initializer (different base types) @@ expected int [signed] p @@ got restint [signed] p @@
net/ipv6/route.c:4735:29: expected int [signed] p
net/ipv6/route.c:4735:29: got restricted __be16
>> net/ipv6/route.c:4740:15: sparse: incorrect type in assignment (different base types) @@ expected restricted __be16 [usertype] <noident> @@ got 6 [usertype] <noident> @@
net/ipv6/route.c:4740:15: expected restricted __be16 [usertype] <noident>
net/ipv6/route.c:4740:15: got int [signed] p
net/ipv6/route.c:3196:12: sparse: context imbalance in 'ip6_route_del' - wrong count at exit
vim +4735 net/ipv6/route.c
4732
4733 static int nla_get_port(struct nlattr *attr, __be16 *port)
4734 {
> 4735 int p = nla_get_be16(attr);
4736
4737 if (p <= 0 || p >= 0xffff)
4738 return -EINVAL;
4739
> 4740 *port = p;
4741 return 0;
4742 }
4743
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-05-07 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 0:59 [PATCH net-next v2 0/3] fib rule selftest Roopa Prabhu
2018-05-07 0:59 ` [PATCH net-next v2 1/3] ipv4: support sport and dport in RTM_GETROUTE Roopa Prabhu
2018-05-07 1:46 ` David Ahern
2018-05-07 14:42 ` Roopa Prabhu
2018-05-07 5:49 ` kbuild test robot
2018-05-07 0:59 ` [PATCH net-next v2 2/3] ipv6: " Roopa Prabhu
2018-05-07 1:46 ` David Ahern
2018-05-07 6:23 ` kbuild test robot [this message]
2018-05-07 0:59 ` [PATCH net-next v2 3/3] selftests: net: initial fib rule tests Roopa Prabhu
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=201805071454.M3MseL9U%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=idosch@mellanox.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
/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