From: kernel test robot <lkp@intel.com>
To: Lev Pantiukhin <kndrvt@yandex-team.ru>
Cc: oe-kbuild-all@lists.linux.dev, mitradir@yandex-team.ru,
Lev Pantiukhin <kndrvt@yandex-team.ru>,
Simon Horman <horms@verge.net.au>, Julian Anastasov <ja@ssi.bg>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
lvs-devel@vger.kernel.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org
Subject: Re: [PATCH] ipvs: add a stateless type of service and a stateless Maglev hashing scheduler
Date: Wed, 6 Dec 2023 18:52:50 +0800 [thread overview]
Message-ID: <202312061823.O99VPf15-lkp@intel.com> (raw)
In-Reply-To: <20231204152020.472247-1-kndrvt@yandex-team.ru>
Hi Lev,
kernel test robot noticed the following build warnings:
[auto build test WARNING on horms-ipvs-next/master]
[also build test WARNING on horms-ipvs/master linus/master v6.7-rc4 next-20231206]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Lev-Pantiukhin/ipvs-add-a-stateless-type-of-service-and-a-stateless-Maglev-hashing-scheduler/20231204-232344
base: https://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next.git master
patch link: https://lore.kernel.org/r/20231204152020.472247-1-kndrvt%40yandex-team.ru
patch subject: [PATCH] ipvs: add a stateless type of service and a stateless Maglev hashing scheduler
config: microblaze-randconfig-r123-20231206 (https://download.01.org/0day-ci/archive/20231206/202312061823.O99VPf15-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231206/202312061823.O99VPf15-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312061823.O99VPf15-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> net/netfilter/ipvs/ip_vs_ctl.c:972:42: sparse: sparse: restricted __be32 degrades to integer
net/netfilter/ipvs/ip_vs_ctl.c:972:60: sparse: sparse: restricted __be32 degrades to integer
net/netfilter/ipvs/ip_vs_ctl.c:976:48: sparse: sparse: restricted __be32 degrades to integer
net/netfilter/ipvs/ip_vs_ctl.c:976:70: sparse: sparse: restricted __be32 degrades to integer
>> net/netfilter/ipvs/ip_vs_ctl.c:976:30: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be32 [usertype] diff @@ got unsigned int @@
net/netfilter/ipvs/ip_vs_ctl.c:976:30: sparse: expected restricted __be32 [usertype] diff
net/netfilter/ipvs/ip_vs_ctl.c:976:30: sparse: got unsigned int
>> net/netfilter/ipvs/ip_vs_ctl.c:978:41: sparse: sparse: cast from restricted __be32
net/netfilter/ipvs/ip_vs_ctl.c:1532:27: sparse: sparse: dereference of noderef expression
vim +972 net/netfilter/ipvs/ip_vs_ctl.c
962
963 static int __ip_vs_mh_compare_dests(struct list_head *a, struct list_head *b)
964 {
965 struct ip_vs_dest *dest_a = list_entry(a, struct ip_vs_dest, n_list);
966 struct ip_vs_dest *dest_b = list_entry(b, struct ip_vs_dest, n_list);
967 unsigned int i = 0;
968 __be32 diff;
969
970 switch (dest_a->af) {
971 case AF_INET:
> 972 return (int)(dest_a->addr.ip - dest_b->addr.ip);
973
974 case AF_INET6:
975 for (; i < ARRAY_SIZE(dest_a->addr.ip6); i++) {
> 976 diff = dest_a->addr.ip6[i] - dest_b->addr.ip6[i];
977 if (diff)
> 978 return (int)diff;
979 }
980 }
981
982 return 0;
983 }
984
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-06 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 15:20 [PATCH] ipvs: add a stateless type of service and a stateless Maglev hashing scheduler Lev Pantiukhin
2023-12-05 20:03 ` Julian Anastasov
2023-12-06 10:52 ` kernel test robot [this message]
2023-12-06 12:33 ` Julian Anastasov
2023-12-07 5:33 ` Dan Carpenter
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=202312061823.O99VPf15-lkp@intel.com \
--to=lkp@intel.com \
--cc=coreteam@netfilter.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=kadlec@netfilter.org \
--cc=kndrvt@yandex-team.ru \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvs-devel@vger.kernel.org \
--cc=mitradir@yandex-team.ru \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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).