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: <56390E01.6050104@amd.com>
Date:	Tue, 3 Nov 2015 13:41:53 -0600
From:	Aravind Gopalakrishnan <aravind.gopalakrishnan@....com>
To:	kbuild test robot <lkp@...el.com>
CC:	<kbuild-all@...org>, <tglx@...utronix.de>, <mingo@...hat.com>,
	<hpa@...or.com>, <bp@...e.de>, <x86@...nel.org>,
	<sudeep.holla@....com>, <akpm@...ux-foundation.org>,
	<geliangtang@....com>, <tj@...nel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/intel_cacheinfo: Fix LLC topology for AMD Fam17h
 systems

On 11/3/2015 1:27 PM, kbuild test robot wrote:
> Hi Aravind,
>
> [auto build test ERROR on bp/for-next]
> [also ERROR on: v4.3 next-20151103]
>
> url:    https://github.com/0day-ci/linux/commits/Aravind-Gopalakrishnan/x86-intel_cacheinfo-Fix-LLC-topology-for-AMD-Fam17h-systems/20151104-031725
> base:   https://github.com/0day-ci/linux Aravind-Gopalakrishnan/x86-intel_cacheinfo-Fix-LLC-topology-for-AMD-Fam17h-systems/20151104-031725
> config: i386-tinyconfig (attached as .config)
> reproduce:
>          # save the attached .config to linux build tree
>          make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
>     arch/x86/built-in.o: In function `init_amd_cacheinfo':
>>> (.text+0x6aec): undefined reference to `cpu_llc_id'
>

Thanks for the catch!

cpu_llc_id references should be wrapped under #ifdef CONFIG_SMP.

Did that and kernel build worked with the attached config.

Will send a V2 with the fix.

Thanks,
-Aravind.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ