From: kernel test robot <lkp@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH v2 1/2] net: extend drop reasons for multiple subsystems
Date: Fri, 14 Apr 2023 11:21:59 +0800 [thread overview]
Message-ID: <202304141104.ixaAlfxh-lkp@intel.com> (raw)
In-Reply-To: <20230330212227.928595-1-johannes@sipsolutions.net>
Hi Johannes,
kernel test robot noticed the following build warnings:
[auto build test WARNING on wireless-next/main]
[also build test WARNING on wireless/main horms-ipvs/master net/main net-next/main linus/master v6.3-rc6 next-20230413]
[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/Johannes-Berg/mac80211-use-the-new-drop-reasons-infrastructure/20230331-052445
base: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
patch link: https://lore.kernel.org/r/20230330212227.928595-1-johannes%40sipsolutions.net
patch subject: [PATCH v2 1/2] net: extend drop reasons for multiple subsystems
config: m68k-randconfig-s042-20230413 (https://download.01.org/0day-ci/archive/20230414/202304141104.ixaAlfxh-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 12.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/intel-lab-lkp/linux/commit/64925179be74db98280d706236e37e05bf7b5cca
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Johannes-Berg/mac80211-use-the-new-drop-reasons-infrastructure/20230331-052445
git checkout 64925179be74db98280d706236e37e05bf7b5cca
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=m68k olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=m68k SHELL=/bin/bash net/core/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304141104.ixaAlfxh-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> net/core/skbuff.c:138:42: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct drop_reason_list const [noderef] __rcu * @@ got struct drop_reason_list const * @@
net/core/skbuff.c:138:42: sparse: expected struct drop_reason_list const [noderef] __rcu *
net/core/skbuff.c:138:42: sparse: got struct drop_reason_list const *
vim +138 net/core/skbuff.c
135
136 const struct drop_reason_list __rcu *
137 drop_reasons_by_subsys[SKB_DROP_REASON_SUBSYS_NUM] = {
> 138 [SKB_DROP_REASON_SUBSYS_CORE] = &drop_reasons_core,
139 };
140 EXPORT_SYMBOL(drop_reasons_by_subsys);
141
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
prev parent reply other threads:[~2023-04-14 3:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 21:22 [PATCH v2 1/2] net: extend drop reasons for multiple subsystems Johannes Berg
2023-03-30 21:22 ` [PATCH v2 2/2] mac80211: use the new drop reasons infrastructure Johannes Berg
2023-04-01 4:36 ` [PATCH v2 1/2] net: extend drop reasons for multiple subsystems Jakub Kicinski
2023-04-14 9:25 ` Johannes Berg
2023-04-14 14:42 ` Jakub Kicinski
2023-04-14 3:21 ` kernel test robot [this message]
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=202304141104.ixaAlfxh-lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@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 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).