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] [thread-next>] [day] [month] [year] [list]
Message-ID: <874jdpwm0x.ffs@tglx>
Date: Sat, 02 Mar 2024 00:49:18 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: kernel test robot <lkp@...el.com>
Cc: oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: arch/x86/kernel/cpu/debugfs.c:11:33: sparse: sparse: incorrect
 type in initializer (different address spaces)

On Sat, Mar 02 2024 at 07:38, kernel test robot wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   d17468c6f1f49e6259698f6401b8d7a5b90eac68
> commit: 48525fd1ea1cfa059a580e77b10ea8790914efa2 x86/cpu: Provide debug interface
> date:   5 months ago
> config: x86_64-randconfig-121-20240301 (https://download.01.org/0day-ci/archive/20240302/202403020747.CxX5V2dB-lkp@intel.com/config)
> compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240302/202403020747.CxX5V2dB-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@...el.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202403020747.CxX5V2dB-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
>
>
> vim +11 arch/x86/kernel/cpu/debugfs.c
>
>      7	
>      8	static int cpu_debug_show(struct seq_file *m, void *p)
>      9	{
>     10		unsigned long cpu = (unsigned long)m->private;
>   > 11		struct cpuinfo_x86 *c = per_cpu_ptr(&cpu_info, cpu);

This is the line which allegdly causes that new bogus warning, but your
report does not include the warning itself. How useful...

Though don't bother to send me the warning. It's going to be completely
bogus anyway as all the other ones.

Thanks,

        tglx


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ