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: llvm@lists.linux.dev, 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 08:28:15 +0800 [thread overview]
Message-ID: <202604150808.7HxFp5b4-lkp@intel.com> (raw)
In-Reply-To: <20260404074103.506793-1-youling.tang@linux.dev>
Hi Youling,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING 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: loongarch-randconfig-001-20260415 (https://download.01.org/0day-ci/archive/20260415/202604150808.7HxFp5b4-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260415/202604150808.7HxFp5b4-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/202604150808.7HxFp5b4-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/crash_reserve.c:264:19: warning: expression which evaluates to zero treated as a null pointer constant of type 'char *' [-Wnon-literal-null-conversion]
264 | char *first_gt = false;
| ^~~~~
1 warning generated.
vim +264 kernel/crash_reserve.c
254
255 /*
256 * This function parses command lines in the format
257 *
258 * crashkernel=ramsize-range:size[,...][@offset],>boundary
259 */
260 static void __init parse_crashkernel_boundary(char *ck_cmdline,
261 unsigned long long *boundary)
262 {
263 char *cur = ck_cmdline, *next;
> 264 char *first_gt = false;
265
266 first_gt = strchr(cur, '>');
267 if (!first_gt)
268 return;
269
270 cur = first_gt + 1;
271 if (*cur == '\0' || *cur == ' ' || *cur == ',') {
272 pr_warn("crashkernel: '>' specified without boundary size, ignoring\n");
273 return;
274 }
275
276 *boundary = memparse(cur, &next);
277 if (cur == next) {
278 pr_warn("crashkernel: invalid boundary size after '>'\n");
279 return;
280 }
281 }
282
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-04-15 0:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2026-04-15 1:43 ` kernel test robot
2026-04-15 3:17 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2026-04-14 20:16 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=202604150808.7HxFp5b4-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=llvm@lists.linux.dev \
--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 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.