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] [day] [month] [year] [list]
Message-ID: <aV5s9MOkYzjeNNbs@willie-the-truck>
Date: Wed, 7 Jan 2026 14:25:56 +0000
From: Will Deacon <will@...nel.org>
To: kernel test robot <lkp@...el.com>
Cc: Marc Zyngier <maz@...nel.org>, oe-kbuild-all@...ts.linux.dev,
	linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: Re: arch/arm64/kernel/cpufeature.c:3095:9: sparse: sparse:
 Initializer entry defined twice

On Mon, Dec 15, 2025 at 05:39:33PM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   8f0b4cce4481fb22653697cced8d0d04027cb1e8
> commit: 064737920bdbca86df91b96aed256e88018fef3a arm64: Filter out SVE hwcaps when FEAT_SVE isn't implemented
> date:   11 months ago
> config: arm64-randconfig-r112-20251214 (https://download.01.org/0day-ci/archive/20251215/202512151716.VtbG1F7H-lkp@intel.com/config)
> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251215/202512151716.VtbG1F7H-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/202512151716.VtbG1F7H-lkp@intel.com/
> 
> sparse warnings: (new ones prefixed by >>)
> >> arch/arm64/kernel/cpufeature.c:3095:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3095:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3096:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3096:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3097:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3097:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3098:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3098:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3099:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3099:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3100:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3100:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3101:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3101:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3102:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3102:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3103:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3103:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3104:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3104:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3105:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3105:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3106:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3106:9: sparse:   also defined here
>    arch/arm64/kernel/cpufeature.c:3107:9: sparse: sparse: Initializer entry defined twice
>    arch/arm64/kernel/cpufeature.c:3107:9: sparse:   also defined here

I think this is just because we override the '.matches' callback with
'has_sve_feature' after first initialising it to 'has_user_cpuid_feature',
so there's not a functional issue here.

However, maybe the diff below would squash the warning?

Will

--->8

diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
index c840a93b9ef9..054f024ac926 100644
--- a/arch/arm64/kernel/cpufeature.c
+++ b/arch/arm64/kernel/cpufeature.c
@@ -3183,7 +3183,7 @@ static const struct arm64_cpu_capabilities arm64_features[] = {
 #define HWCAP_CAP_MATCH_ID(match, reg, field, min_value, cap_type, cap)                \
        {                                                                       \
                __HWCAP_CAP(#cap, cap_type, cap)                                \
-               HWCAP_CPUID_MATCH(reg, field, min_value)                        \
+               ARM64_CPUID_FIELDS(reg, field, min_value)                       \
                .matches = match,                                               \
        }


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ