* Re: [alobakin:iavf-pp-frag 11/28] net/core/page_pool.c:582:9: sparse: sparse: incorrect type in argument 1 (different address spaces) [not found] <202307292029.cFz0s8Hh-lkp@intel.com> @ 2023-08-01 13:46 ` Alexander Lobakin 2023-08-01 16:53 ` Jakub Kicinski 0 siblings, 1 reply; 3+ messages in thread From: Alexander Lobakin @ 2023-08-01 13:46 UTC (permalink / raw) To: Jakub Kicinski; +Cc: kernel test robot, oe-kbuild-all, netdev@vger.kernel.org From: Kernel Test Robot <lkp@intel.com> Date: Sat, 29 Jul 2023 20:30:10 +0800 > tree: https://github.com/alobakin/linux iavf-pp-frag > head: 0eccfd667ed84b425dc0c48eab06b0cb1d5fd8c4 > commit: 67f0169041f76c28d399c2a63947e33a1ae1210d [11/28] page_pool: add a lockdep check for recycling in hardirq > config: loongarch-randconfig-r072-20230728 (https://download.01.org/0day-ci/archive/20230729/202307292029.cFz0s8Hh-lkp@intel.com/config) > compiler: loongarch64-linux-gcc (GCC) 12.3.0 > reproduce: (https://download.01.org/0day-ci/archive/20230729/202307292029.cFz0s8Hh-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/202307292029.cFz0s8Hh-lkp@intel.com/ Jakub, could you take a look, is this warning reasonable? > > sparse warnings: (new ones prefixed by >>) >>> net/core/page_pool.c:582:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *ptr @@ got unsigned int [noderef] __percpu * @@ > net/core/page_pool.c:582:9: sparse: expected void *ptr > net/core/page_pool.c:582:9: sparse: got unsigned int [noderef] __percpu * >>> net/core/page_pool.c:582:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *ptr @@ got unsigned int [noderef] __percpu * @@ > net/core/page_pool.c:582:9: sparse: expected void *ptr > net/core/page_pool.c:582:9: sparse: got unsigned int [noderef] __percpu * >>> net/core/page_pool.c:582:9: sparse: sparse: incorrect type in argument 1 (different address [...] Thanks, Olek ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [alobakin:iavf-pp-frag 11/28] net/core/page_pool.c:582:9: sparse: sparse: incorrect type in argument 1 (different address spaces) 2023-08-01 13:46 ` [alobakin:iavf-pp-frag 11/28] net/core/page_pool.c:582:9: sparse: sparse: incorrect type in argument 1 (different address spaces) Alexander Lobakin @ 2023-08-01 16:53 ` Jakub Kicinski 2023-08-01 17:03 ` Alexander Lobakin 0 siblings, 1 reply; 3+ messages in thread From: Jakub Kicinski @ 2023-08-01 16:53 UTC (permalink / raw) To: Alexander Lobakin Cc: kernel test robot, oe-kbuild-all, netdev@vger.kernel.org, loongarch On Tue, 1 Aug 2023 15:46:22 +0200 Alexander Lobakin wrote: > > 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/202307292029.cFz0s8Hh-lkp@intel.com/ > > Jakub, could you take a look, is this warning reasonable? Doesn't look legit to me. I can't repro it on x86 and: $ head .config # # Automatically generated file; DO NOT EDIT. # Linux/loongarch 6.5.0-rc3 Kernel Configuration # CONFIG_CC_VERSION_TEXT="loongarch64-linux-gcc (GCC) 12.3.0" Adding loongarch to CC, it must be arch specific ? ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [alobakin:iavf-pp-frag 11/28] net/core/page_pool.c:582:9: sparse: sparse: incorrect type in argument 1 (different address spaces) 2023-08-01 16:53 ` Jakub Kicinski @ 2023-08-01 17:03 ` Alexander Lobakin 0 siblings, 0 replies; 3+ messages in thread From: Alexander Lobakin @ 2023-08-01 17:03 UTC (permalink / raw) To: Jakub Kicinski Cc: kernel test robot, oe-kbuild-all, netdev@vger.kernel.org, loongarch From: Jakub Kicinski <kuba@kernel.org> Date: Tue, 1 Aug 2023 09:53:21 -0700 > On Tue, 1 Aug 2023 15:46:22 +0200 Alexander Lobakin wrote: >>> 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/202307292029.cFz0s8Hh-lkp@intel.com/ >> >> Jakub, could you take a look, is this warning reasonable? > > Doesn't look legit to me. I can't repro it on x86 and: > > $ head .config > # > # Automatically generated file; DO NOT EDIT. > # Linux/loongarch 6.5.0-rc3 Kernel Configuration > # > CONFIG_CC_VERSION_TEXT="loongarch64-linux-gcc (GCC) 12.3.0" > > Adding loongarch to CC, it must be arch specific ? Took a look, sounds like something's wrong inside this_cpu_read() on this architecture (probably with some not-widely-used options enabled), dunno. Will wait for the architecture folks, there's nothing to fix in your patch (fully legit and ordinary lockdep expression). Thanks, Olek ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-08-01 17:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <202307292029.cFz0s8Hh-lkp@intel.com>
2023-08-01 13:46 ` [alobakin:iavf-pp-frag 11/28] net/core/page_pool.c:582:9: sparse: sparse: incorrect type in argument 1 (different address spaces) Alexander Lobakin
2023-08-01 16:53 ` Jakub Kicinski
2023-08-01 17:03 ` Alexander Lobakin
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).