[ammarfaizi2-block:arm64/linux/for-next/misc 5/7] arch/arm64/mm/init.c:90:19: error: conflicting type qualifiers for 'arm64_dma_phys_limit'

From: kernel test robot
Date: Tue Mar 08 2022 - 13:54:42 EST


tree: https://github.com/ammarfaizi2/linux-block arm64/linux/for-next/misc
head: 819a47d24b61b5e2d660d19c8798f0f9b4498b73
commit: 031495635b4668f94e964e037ca93d0d38bfde58 [5/7] arm64: Do not defer reserve_crashkernel() for platforms with no DMA memory zones
config: arm64-randconfig-r014-20220308 (https://download.01.org/0day-ci/archive/20220309/202203090241.aj7paWeX-lkp@xxxxxxxxx/config)
compiler: aarch64-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/ammarfaizi2/linux-block/commit/031495635b4668f94e964e037ca93d0d38bfde58
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block arm64/linux/for-next/misc
git checkout 031495635b4668f94e964e037ca93d0d38bfde58
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash arch/arm64/mm/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@xxxxxxxxx>

All errors (new ones prefixed by >>):

>> arch/arm64/mm/init.c:90:19: error: conflicting type qualifiers for 'arm64_dma_phys_limit'
90 | const phys_addr_t arm64_dma_phys_limit = PHYS_MASK + 1;
| ^~~~~~~~~~~~~~~~~~~~
In file included from include/asm-generic/qrwlock.h:14,
from ./arch/arm64/include/generated/asm/qrwlock.h:1,
from arch/arm64/include/asm/spinlock.h:9,
from include/linux/spinlock.h:93,
from include/linux/swap.h:5,
from arch/arm64/mm/init.c:12:
arch/arm64/include/asm/processor.h:102:20: note: previous declaration of 'arm64_dma_phys_limit' with type 'phys_addr_t' {aka 'long long unsigned int'}
102 | extern phys_addr_t arm64_dma_phys_limit;
| ^~~~~~~~~~~~~~~~~~~~


vim +/arm64_dma_phys_limit +90 arch/arm64/mm/init.c

57
58 /*
59 * If the corresponding config options are enabled, we create both ZONE_DMA
60 * and ZONE_DMA32. By default ZONE_DMA covers the 32-bit addressable memory
61 * unless restricted on specific platforms (e.g. 30-bit on Raspberry Pi 4).
62 * In such case, ZONE_DMA32 covers the rest of the 32-bit addressable memory,
63 * otherwise it is empty.
64 *
65 * Memory reservation for crash kernel either done early or deferred
66 * depending on DMA memory zones configs (ZONE_DMA) --
67 *
68 * In absence of ZONE_DMA configs arm64_dma_phys_limit initialized
69 * here instead of max_zone_phys(). This lets early reservation of
70 * crash kernel memory which has a dependency on arm64_dma_phys_limit.
71 * Reserving memory early for crash kernel allows linear creation of block
72 * mappings (greater than page-granularity) for all the memory bank rangs.
73 * In this scheme a comparatively quicker boot is observed.
74 *
75 * If ZONE_DMA configs are defined, crash kernel memory reservation
76 * is delayed until DMA zone memory range size initilazation performed in
77 * zone_sizes_init(). The defer is necessary to steer clear of DMA zone
78 * memory range to avoid overlap allocation. So crash kernel memory boundaries
79 * are not known when mapping all bank memory ranges, which otherwise means
80 * not possible to exclude crash kernel range from creating block mappings
81 * so page-granularity mappings are created for the entire memory range.
82 * Hence a slightly slower boot is observed.
83 *
84 * Note: Page-granularity mapppings are necessary for crash kernel memory
85 * range for shrinking its size via /sys/kernel/kexec_crash_size interface.
86 */
87 #if IS_ENABLED(CONFIG_ZONE_DMA) || IS_ENABLED(CONFIG_ZONE_DMA32)
88 phys_addr_t __ro_after_init arm64_dma_phys_limit;
89 #else
> 90 const phys_addr_t arm64_dma_phys_limit = PHYS_MASK + 1;
91 #endif
92

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@xxxxxxxxxxxx