From: kernel test robot <lkp@intel.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Mike Rapoport <rppt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [rppt:crash-kernel/arm64-remap/v0.1 4/5] arch/arm64/mm/init.c:133:3: error: use of undeclared identifier 'crashkres_protection_possible'
Date: Thu, 18 Aug 2022 07:27:35 +0800 [thread overview]
Message-ID: <202208180702.BgAbSr7d-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git crash-kernel/arm64-remap/v0.1
head: 083629d699170f5a86078d0a7afbe647c3a571cb
commit: 3aaa4a222ab056611236c4c42499d24c8317bc96 [4/5] arm64/mm: remap crash kernel with base pages even if rodata_full disabled
config: arm64-randconfig-r034-20220818 (https://download.01.org/0day-ci/archive/20220818/202208180702.BgAbSr7d-lkp@intel.com/config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project aed5e3bea138ce581d682158eb61c27b3cfdd6ec)
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
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git/commit/?id=3aaa4a222ab056611236c4c42499d24c8317bc96
git remote add rppt https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git
git fetch --no-tags rppt crash-kernel/arm64-remap/v0.1
git checkout 3aaa4a222ab056611236c4c42499d24c8317bc96
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash arch/arm64/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> arch/arm64/mm/init.c:133:3: error: use of undeclared identifier 'crashkres_protection_possible'
crashkres_protection_possible = true;
^
arch/arm64/mm/init.c:151:2: error: use of undeclared identifier 'crashkres_protection_possible'
crashkres_protection_possible = true;
^
2 errors generated.
vim +/crashkres_protection_possible +133 arch/arm64/mm/init.c
119
120 static unsigned long long __init
121 reserve_remap_crashkernel(unsigned long long crash_base,
122 unsigned long long crash_size,
123 unsigned long long crash_max)
124 {
125 unsigned long long size;
126
127 /*
128 * If linear map uses base pages or there is no ZONE_DMA/ZONE_DMA32
129 * the crashk_res will be mapped with PTEs in mmu::map_mem()
130 */
131 if (can_set_direct_map() || IS_ENABLED(CONFIG_KFENCE) ||
132 !have_zone_dma()) {
> 133 crashkres_protection_possible = true;
134 return 0;
135 }
136
137 if (crash_base)
138 return 0;
139
140 size = ALIGN(crash_size, PUD_SIZE);
141
142 crash_base = memblock_phys_alloc_range(size, PUD_SIZE, 0, crash_max);
143 if (!crash_base)
144 return 0;
145
146 if (remap_crashkernel(crash_base, crash_size, size)) {
147 memblock_phys_free(crash_base, size);
148 return 0;
149 }
150
151 crashkres_protection_possible = true;
152 memblock_phys_free(crash_base + crash_size, size - crash_size);
153
154 return crash_base;
155 }
156
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-17 23:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202208180702.BgAbSr7d-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox