netdev - Re: [alobakin:iavf-pp-frag 11/28] net/core/page_pool.c:582:9: sparse: sparse: incorrect type in argument 1 (different address spaces)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Tue, 1 Aug 2023 19:03:56 +0200
From: Alexander Lobakin <aleksander.lobakin@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: kernel test robot <lkp@...el.com>, <oe-kbuild-all@...ts.linux.dev>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	<loongarch@...ts.linux.dev>
Subject: Re: [alobakin:iavf-pp-frag 11/28] net/core/page_pool.c:582:9: sparse:
 sparse: incorrect type in argument 1 (different address spaces)

From: Jakub Kicinski <kuba@...nel.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@...el.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