From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH net-next v2 09/15] net: page_pool: implement GET in the netlink API
Date: Tue, 21 Nov 2023 18:37:31 +0800 [thread overview]
Message-ID: <202311211802.zhmXaacc-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: net/core/netdev-genl-gen.c:16:19: sparse: sparse: decimal constant 4294967295 is between LONG_MAX and ULONG_MAX. For C99 that means long long, C90 compilers are very likely to produce unsigned long (and a warning) here"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20231121000048.789613-10-kuba@kernel.org>
References: <20231121000048.789613-10-kuba@kernel.org>
TO: Jakub Kicinski <kuba@kernel.org>
TO: davem@davemloft.net
CC: netdev@vger.kernel.org
CC: edumazet@google.com
CC: pabeni@redhat.com
CC: almasrymina@google.com
CC: hawk@kernel.org
CC: ilias.apalodimas@linaro.org
CC: dsahern@gmail.com
CC: dtatulea@nvidia.com
CC: Jakub Kicinski <kuba@kernel.org>
Hi Jakub,
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/Jakub-Kicinski/net-page_pool-split-the-page_pool_params-into-fast-and-slow/20231121-092240
base: net-next/main
patch link: https://lore.kernel.org/r/20231121000048.789613-10-kuba%40kernel.org
patch subject: [PATCH net-next v2 09/15] net: page_pool: implement GET in the netlink API
:::::: branch date: 9 hours ago
:::::: commit date: 9 hours ago
config: i386-randconfig-061-20231121 (https://download.01.org/0day-ci/archive/20231121/202311211802.zhmXaacc-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231121/202311211802.zhmXaacc-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/202311211802.zhmXaacc-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> net/core/netdev-genl-gen.c:16:19: sparse: sparse: decimal constant 4294967295 is between LONG_MAX and ULONG_MAX. For C99 that means long long, C90 compilers are very likely to produce unsigned long (and a warning) here
vim +16 net/core/netdev-genl-gen.c
d3d854fd6a1d97 Jakub Kicinski 2023-02-01 12
d4fc6a14e941e3 Jakub Kicinski 2023-11-20 13 /* Integer value ranges */
d4fc6a14e941e3 Jakub Kicinski 2023-11-20 14 static const struct netlink_range_validation netdev_a_page_pool_id_range = {
d4fc6a14e941e3 Jakub Kicinski 2023-11-20 15 .min = 1,
d4fc6a14e941e3 Jakub Kicinski 2023-11-20 @16 .max = 4294967295,
d4fc6a14e941e3 Jakub Kicinski 2023-11-20 17 };
d4fc6a14e941e3 Jakub Kicinski 2023-11-20 18
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-11-21 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 10:37 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-21 0:00 [PATCH net-next v2 00/15] net: page_pool: add netlink-based introspection Jakub Kicinski
2023-11-21 0:00 ` [PATCH net-next v2 09/15] net: page_pool: implement GET in the netlink API Jakub Kicinski
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=202311211802.zhmXaacc-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.