From: kernel test robot <lkp@intel.com>
To: Youling Tang <youling.tang@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Jonathan Corbet <corbet@lwn.net>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Vivek Goyal <vgoyal@redhat.com>, Dave Young <dyoung@redhat.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, youling.tang@linux.dev,
Youling Tang <tangyouling@kylinos.cn>
Subject: Re: [PATCH] crash: Support high memory reservation for range syntax
Date: Wed, 15 Apr 2026 11:17:53 +0800 [thread overview]
Message-ID: <202604151100.7wbci6vo-lkp@intel.com> (raw)
In-Reply-To: <20260404074103.506793-1-youling.tang@linux.dev>
Hi Youling,
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on linus/master v7.0 next-20260414]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Youling-Tang/crash-Support-high-memory-reservation-for-range-syntax/20260414-205035
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20260404074103.506793-1-youling.tang%40linux.dev
patch subject: [PATCH] crash: Support high memory reservation for range syntax
config: mips-randconfig-r061-20260415 (https://download.01.org/0day-ci/archive/20260415/202604151100.7wbci6vo-lkp@intel.com/config)
compiler: mips64-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260415/202604151100.7wbci6vo-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@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202604151100.7wbci6vo-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/crash_reserve.c: In function '__parse_crashkernel':
>> kernel/crash_reserve.c:324:37: error: 'DEFAULT_CRASH_KERNEL_LOW_SIZE' undeclared (first use in this function)
324 | *low_size = DEFAULT_CRASH_KERNEL_LOW_SIZE;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
kernel/crash_reserve.c:324:37: note: each undeclared identifier is reported only once for each function it appears in
vim +/DEFAULT_CRASH_KERNEL_LOW_SIZE +324 kernel/crash_reserve.c
282
283 static int __init __parse_crashkernel(char *cmdline,
284 unsigned long long system_ram,
285 unsigned long long *crash_size,
286 unsigned long long *crash_base,
287 const char *suffix,
288 bool *high,
289 unsigned long long *low_size)
290 {
291 char *first_colon, *first_space;
292 char *ck_cmdline;
293 char *name = "crashkernel=";
294 unsigned long long boundary = 0;
295 int ret;
296
297 BUG_ON(!crash_size || !crash_base);
298 *crash_size = 0;
299 *crash_base = 0;
300
301 ck_cmdline = get_last_crashkernel(cmdline, name, suffix);
302 if (!ck_cmdline)
303 return -ENOENT;
304
305 ck_cmdline += strlen(name);
306
307 if (suffix)
308 return parse_crashkernel_suffix(ck_cmdline, crash_size,
309 suffix);
310 /*
311 * if the commandline contains a ':', then that's the extended
312 * syntax -- if not, it must be the classic syntax
313 */
314 first_colon = strchr(ck_cmdline, ':');
315 first_space = strchr(ck_cmdline, ' ');
316 if (first_colon && (!first_space || first_colon < first_space)) {
317 ret = parse_crashkernel_mem(ck_cmdline, system_ram,
318 crash_size, crash_base);
319
320 /* Handle optional ',>boundary' condition for range ':' syntax only. */
321 parse_crashkernel_boundary(ck_cmdline, &boundary);
322 if (!ret && *crash_size > boundary) {
323 *high = true;
> 324 *low_size = DEFAULT_CRASH_KERNEL_LOW_SIZE;
325 }
326
327 return ret;
328 }
329
330 return parse_crashkernel_simple(ck_cmdline, crash_size, crash_base);
331 }
332
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-04-15 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260404074103.506793-1-youling.tang@linux.dev>
2026-04-15 0:28 ` kernel test robot
2026-04-15 1:43 ` kernel test robot
2026-04-15 3:17 ` kernel test robot [this message]
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=202604151100.7wbci6vo-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tangyouling@kylinos.cn \
--cc=vgoyal@redhat.com \
--cc=youling.tang@linux.dev \
/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