From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: kernel/kexec_core.c:1253 crash_cma_ranges_show() warn: we never enter this loop
Date: Thu, 05 Mar 2026 07:39:49 +0800 [thread overview]
Message-ID: <202603050703.t77oFseJ-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Sourabh Jain <sourabhjain@linux.ibm.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ecc64d2dc9ff9738d2a896beb68e02c2feaf9a02
commit: cf4340bdd967fe7f37b4361c85370515f11f4a37 kexec: move sysfs entries to /sys/kernel/kexec
date: 3 months ago
:::::: branch date: 7 hours ago
:::::: commit date: 3 months ago
config: i386-randconfig-141-20260305 (https://download.01.org/0day-ci/archive/20260305/202603050703.t77oFseJ-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
smatch: v0.5.0-9004-gb810ac53
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202603050703.t77oFseJ-lkp@intel.com/
smatch warnings:
kernel/kexec_core.c:1253 crash_cma_ranges_show() warn: we never enter this loop
vim +1253 kernel/kexec_core.c
cf4340bdd967fe Sourabh Jain 2025-11-18 1249
cf4340bdd967fe Sourabh Jain 2025-11-18 1250 ssize_t len = 0;
cf4340bdd967fe Sourabh Jain 2025-11-18 1251 int i;
cf4340bdd967fe Sourabh Jain 2025-11-18 1252
cf4340bdd967fe Sourabh Jain 2025-11-18 @1253 for (i = 0; i < crashk_cma_cnt; ++i) {
cf4340bdd967fe Sourabh Jain 2025-11-18 1254 len += sysfs_emit_at(buf, len, "%08llx-%08llx\n",
cf4340bdd967fe Sourabh Jain 2025-11-18 1255 crashk_cma_ranges[i].start,
cf4340bdd967fe Sourabh Jain 2025-11-18 1256 crashk_cma_ranges[i].end);
cf4340bdd967fe Sourabh Jain 2025-11-18 1257 }
cf4340bdd967fe Sourabh Jain 2025-11-18 1258 return len;
cf4340bdd967fe Sourabh Jain 2025-11-18 1259 }
cf4340bdd967fe Sourabh Jain 2025-11-18 1260 static struct kobj_attribute crash_cma_ranges_attr = __ATTR_RO(crash_cma_ranges);
cf4340bdd967fe Sourabh Jain 2025-11-18 1261 #endif
cf4340bdd967fe Sourabh Jain 2025-11-18 1262
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-04 23:40 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=202603050703.t77oFseJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.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.