linux-kernel - Re: WARNING: arch/arm64/kernel/cpufeature.c:3369 this_cpu_has

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 for Android: free password hash cracker in your pocket

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

Message-ID: <87il2sw4tj.wl-maz@kernel.org>
Date: Tue, 13 Feb 2024 19:18:48 +0000
From: Marc Zyngier <maz@...nel.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Linux ARM <linux-arm-kernel@...ts.infradead.org>,
	Linux Regressions <regressions@...ts.linux.dev>,
	open list <linux-kernel@...r.kernel.org>,
	lkft-triage@...ts.linaro.org,
	Suzuki K Poulose <suzuki.poulose@....com>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Catalin Marinas <catalin.marinas@....com>
Subject: Re: WARNING: arch/arm64/kernel/cpufeature.c:3369 this_cpu_has_cap

On Tue, 13 Feb 2024 18:21:23 +0000,
Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> 
> Following kernel warning notices on all arm64 devices on today's Linux
> next-20240213 tag.
> 
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>

What is the sense of this tag, and even of this email, for an issue
that has already been reported, as outlined below?

> 
> [    0.038524] SMP: Total of 6 processors activated.
> [    0.038539] CPU: All CPU(s) started at EL2
> [    0.038588] CPU features: detected: 32-bit EL0 Support
> [    0.038602] CPU features: detected: 32-bit EL1 Support
> [    0.038620] CPU features: detected: CRC32 instructions
> [    0.038650] ------------[ cut here ]------------
> [    0.038656] WARNING: CPU: 0 PID: 1 at
> arch/arm64/kernel/cpufeature.c:3369 this_cpu_has_cap+0x1c/0x70
> [    0.038691] Modules linked in:
> [    0.038707] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> 6.8.0-rc4-next-20240213 #1
> [    0.038721] Hardware name: Radxa ROCK Pi 4B (DT)
> [    0.038729] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [    0.038744] pc : this_cpu_has_cap+0x1c/0x70
> [    0.038761] lr : has_nv1+0x28/0xe8
> ..
> [    0.039008] Call trace:
> [    0.039014]  this_cpu_has_cap+0x1c/0x70
> [    0.039031]  update_cpu_capabilities+0xd4/0x138
> [    0.039048]  setup_system_features+0x38/0x130
> [    0.039075]  smp_cpus_done+0x50/0xc8
> [    0.039094]  smp_init+0x84/0xa0
> [    0.039109]  kernel_init_freeable+0x11c/0x400
> [    0.039126]  kernel_init+0x28/0x1f0
> [    0.039148]  ret_from_fork+0x10/0x20
> [    0.039167] ---[ end trace 0000000000000000 ]---
> 
> 
> Links:
>  - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240213/testrun/22596318/suite/log-parser-boot/test/check-kernel-exception/log
>  - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240213/testrun/22596318/suite/log-parser-boot/tests/
> 
> This issue has been addressed in the relevant email thread,
> https://lore.kernel.org/all/0593516b-2419-49b7-83aa-fe189ffad0c2@arm.com/

Correct link:

https://lore.kernel.org/all/86bk8k5ts3.wl-maz@kernel.org/

> I will test the corresponding fix patch and get back to you.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.