From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH] crash: Support high memory reservation for range syntax
Date: Tue, 14 Apr 2026 22:16:08 +0200 [thread overview]
Message-ID: <202604142220.dKz92tzW-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260404074103.506793-1-youling.tang@linux.dev>
References: <20260404074103.506793-1-youling.tang@linux.dev>
TO: Youling Tang <youling.tang@linux.dev>
TO: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
TO: Baoquan He <bhe@redhat.com>
TO: Jonathan Corbet <corbet@lwn.net>
CC: Vivek Goyal <vgoyal@redhat.com>
CC: Dave Young <dyoung@redhat.com>
CC: kexec@lists.infradead.org
CC: linux-kernel@vger.kernel.org
CC: linux-doc@vger.kernel.org
CC: youling.tang@linux.dev
CC: Youling Tang <tangyouling@kylinos.cn>
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
:::::: branch date: 7 hours ago
:::::: commit date: 7 hours ago
config: s390-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260414/202604142220.dKz92tzW-lkp@intel.com/config)
compiler: s390x-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260414/202604142220.dKz92tzW-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/r/202604142220.dKz92tzW-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
b83e6224c4967a Youling Tang 2026-04-04 282
85fcde402db191 Baoquan He 2024-01-24 283 static int __init __parse_crashkernel(char *cmdline,
85fcde402db191 Baoquan He 2024-01-24 284 unsigned long long system_ram,
85fcde402db191 Baoquan He 2024-01-24 285 unsigned long long *crash_size,
85fcde402db191 Baoquan He 2024-01-24 286 unsigned long long *crash_base,
b83e6224c4967a Youling Tang 2026-04-04 287 const char *suffix,
b83e6224c4967a Youling Tang 2026-04-04 288 bool *high,
b83e6224c4967a Youling Tang 2026-04-04 289 unsigned long long *low_size)
85fcde402db191 Baoquan He 2024-01-24 290 {
85fcde402db191 Baoquan He 2024-01-24 291 char *first_colon, *first_space;
85fcde402db191 Baoquan He 2024-01-24 292 char *ck_cmdline;
85fcde402db191 Baoquan He 2024-01-24 293 char *name = "crashkernel=";
b83e6224c4967a Youling Tang 2026-04-04 294 unsigned long long boundary = 0;
b83e6224c4967a Youling Tang 2026-04-04 295 int ret;
85fcde402db191 Baoquan He 2024-01-24 296
85fcde402db191 Baoquan He 2024-01-24 297 BUG_ON(!crash_size || !crash_base);
85fcde402db191 Baoquan He 2024-01-24 298 *crash_size = 0;
85fcde402db191 Baoquan He 2024-01-24 299 *crash_base = 0;
85fcde402db191 Baoquan He 2024-01-24 300
85fcde402db191 Baoquan He 2024-01-24 301 ck_cmdline = get_last_crashkernel(cmdline, name, suffix);
85fcde402db191 Baoquan He 2024-01-24 302 if (!ck_cmdline)
85fcde402db191 Baoquan He 2024-01-24 303 return -ENOENT;
85fcde402db191 Baoquan He 2024-01-24 304
85fcde402db191 Baoquan He 2024-01-24 305 ck_cmdline += strlen(name);
85fcde402db191 Baoquan He 2024-01-24 306
85fcde402db191 Baoquan He 2024-01-24 307 if (suffix)
85fcde402db191 Baoquan He 2024-01-24 308 return parse_crashkernel_suffix(ck_cmdline, crash_size,
85fcde402db191 Baoquan He 2024-01-24 309 suffix);
85fcde402db191 Baoquan He 2024-01-24 310 /*
85fcde402db191 Baoquan He 2024-01-24 311 * if the commandline contains a ':', then that's the extended
85fcde402db191 Baoquan He 2024-01-24 312 * syntax -- if not, it must be the classic syntax
85fcde402db191 Baoquan He 2024-01-24 313 */
85fcde402db191 Baoquan He 2024-01-24 314 first_colon = strchr(ck_cmdline, ':');
85fcde402db191 Baoquan He 2024-01-24 315 first_space = strchr(ck_cmdline, ' ');
b83e6224c4967a Youling Tang 2026-04-04 316 if (first_colon && (!first_space || first_colon < first_space)) {
b83e6224c4967a Youling Tang 2026-04-04 317 ret = parse_crashkernel_mem(ck_cmdline, system_ram,
85fcde402db191 Baoquan He 2024-01-24 318 crash_size, crash_base);
85fcde402db191 Baoquan He 2024-01-24 319
b83e6224c4967a Youling Tang 2026-04-04 320 /* Handle optional ',>boundary' condition for range ':' syntax only. */
b83e6224c4967a Youling Tang 2026-04-04 321 parse_crashkernel_boundary(ck_cmdline, &boundary);
b83e6224c4967a Youling Tang 2026-04-04 322 if (!ret && *crash_size > boundary) {
b83e6224c4967a Youling Tang 2026-04-04 323 *high = true;
b83e6224c4967a Youling Tang 2026-04-04 @324 *low_size = DEFAULT_CRASH_KERNEL_LOW_SIZE;
b83e6224c4967a Youling Tang 2026-04-04 325 }
b83e6224c4967a Youling Tang 2026-04-04 326
b83e6224c4967a Youling Tang 2026-04-04 327 return ret;
b83e6224c4967a Youling Tang 2026-04-04 328 }
b83e6224c4967a Youling Tang 2026-04-04 329
85fcde402db191 Baoquan He 2024-01-24 330 return parse_crashkernel_simple(ck_cmdline, crash_size, crash_base);
85fcde402db191 Baoquan He 2024-01-24 331 }
85fcde402db191 Baoquan He 2024-01-24 332
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-04-14 20:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 20:16 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-04 7:41 [PATCH] crash: Support high memory reservation for range syntax Youling Tang
2026-04-08 4:31 ` Sourabh Jain
2026-04-08 7:41 ` Youling Tang
2026-04-08 9:40 ` Sourabh Jain
2026-04-08 13:32 ` Baoquan He
2026-04-09 1:55 ` Youling Tang
2026-04-15 11:29 ` Baoquan He
2026-04-17 9:23 ` Youling Tang
2026-04-08 11:32 ` Sourabh Jain
2026-04-15 0:28 ` kernel test robot
2026-04-15 1:43 ` kernel test robot
2026-04-15 3:17 ` kernel test robot
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=202604142220.dKz92tzW-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.