From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH net-next] flow_dissector: Add IPSEC dissectors
Date: Tue, 25 Jul 2023 22:36:20 +0800 [thread overview]
Message-ID: <202307252253.1DutjtIg-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: include/net/flow_dissector.h:442:50: sparse: sparse: shift too big (32) for type int"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20230725032451.505189-1-rkannoth@marvell.com>
References: <20230725032451.505189-1-rkannoth@marvell.com>
TO: Ratheesh Kannoth <rkannoth@marvell.com>
TO: netdev@vger.kernel.org
TO: linux-kernel@vger.kernel.org
CC: jhs@mojatatu.com
CC: xiyou.wangcong@gmail.com
CC: jiri@resnulli.us
CC: davem@davemloft.net
CC: edumazet@google.com
CC: kuba@kernel.org
CC: pabeni@redhat.com
CC: Ratheesh Kannoth <rkannoth@marvell.com>
Hi Ratheesh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Ratheesh-Kannoth/flow_dissector-Add-IPSEC-dissectors/20230725-112644
base: net-next/main
patch link: https://lore.kernel.org/r/20230725032451.505189-1-rkannoth%40marvell.com
patch subject: [PATCH net-next] flow_dissector: Add IPSEC dissectors
:::::: branch date: 11 hours ago
:::::: commit date: 11 hours ago
config: powerpc-randconfig-r093-20230725 (https://download.01.org/0day-ci/archive/20230725/202307252253.1DutjtIg-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230725/202307252253.1DutjtIg-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/r/202307252253.1DutjtIg-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
net/core/flow_dissector.c: note: in included file (through include/linux/if_pppox.h):
include/uapi/linux/if_pppox.h:153:29: sparse: sparse: array of flexible structures
net/core/flow_dissector.c: note: in included file (through include/linux/skbuff.h):
>> include/net/flow_dissector.h:442:50: sparse: sparse: shift too big (32) for type int
vim +442 include/net/flow_dissector.h
bcc83839ffdb06 Tom Herbert 2015-09-01 433
c6cc1ca7f4d70c Tom Herbert 2015-09-01 434 u32 flow_hash_from_keys(struct flow_keys *keys);
5dec597e5cd0f4 Matteo Croce 2019-10-29 435 void skb_flow_get_icmp_tci(const struct sk_buff *skb,
5dec597e5cd0f4 Matteo Croce 2019-10-29 436 struct flow_dissector_key_icmp *key_icmp,
f96533cded173b Alexander Lobakin 2021-03-14 437 const void *data, int thoff, int hlen);
c6cc1ca7f4d70c Tom Herbert 2015-09-01 438
8de2d793daf784 Amir Vadai 2016-03-08 439 static inline bool dissector_uses_key(const struct flow_dissector *flow_dissector,
8de2d793daf784 Amir Vadai 2016-03-08 440 enum flow_dissector_key_id key_id)
8de2d793daf784 Amir Vadai 2016-03-08 441 {
8de2d793daf784 Amir Vadai 2016-03-08 @442 return flow_dissector->used_keys & (1 << key_id);
8de2d793daf784 Amir Vadai 2016-03-08 443 }
8de2d793daf784 Amir Vadai 2016-03-08 444
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-07-25 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 14:36 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-25 3:24 [PATCH net-next] flow_dissector: Add IPSEC dissectors Ratheesh Kannoth
2023-07-25 5:11 ` Leon Romanovsky
2023-07-25 10:12 ` Ido Schimmel
2023-07-25 19:50 ` Simon Horman
2023-07-26 6:34 ` Ratheesh Kannoth
2023-07-26 7:38 ` Simon Horman
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=202307252253.1DutjtIg-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.