From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
Subject: mm/cma.c:770:24-29: ERROR: iterator variable bound on line 768 cannot be NULL
Date: Tue, 30 Jun 2026 01:32:49 +0800 [thread overview]
Message-ID: <202606300158.lMSr2D6Z-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: "Yury Norov (NVIDIA)" <yury.norov@gmail.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: dc59e4fea9d83f03bad6bddf3fa2e52491777482
commit: 77c50f9147eabcf726f62c73167bb9d9e8621a43 mm: cma: simplify cma_debug_show_areas()
date: 11 months ago
:::::: branch date: 22 hours ago
:::::: commit date: 11 months ago
config: sh-randconfig-r062-20260629 (https://download.01.org/0day-ci/archive/20260630/202606300158.lMSr2D6Z-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 16.1.0
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
| Fixes: 77c50f9147ea ("mm: cma: simplify cma_debug_show_areas()")
| Reported-by: kernel test robot <lkp@intel.com>
| Reported-by: Julia Lawall <julia.lawall@inria.fr>
| Closes: https://lore.kernel.org/r/202606300158.lMSr2D6Z-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> mm/cma.c:770:24-29: ERROR: iterator variable bound on line 768 cannot be NULL
vim +770 mm/cma.c
c009da4258f988 Frank van der Linden 2025-02-28 751
dbe43d4d2837da Jaewon Kim 2017-02-24 752 static void cma_debug_show_areas(struct cma *cma)
dbe43d4d2837da Jaewon Kim 2017-02-24 753 {
77c50f9147eabc Yury Norov (NVIDIA 2025-07-19 754) unsigned long start, end;
7365ff2c8eef4e Frank van der Linden 2025-02-28 755 unsigned long nr_part;
c009da4258f988 Frank van der Linden 2025-02-28 756 unsigned long nbits;
c009da4258f988 Frank van der Linden 2025-02-28 757 int r;
c009da4258f988 Frank van der Linden 2025-02-28 758 struct cma_memrange *cmr;
dbe43d4d2837da Jaewon Kim 2017-02-24 759
0ef7dcac998fef Mike Kravetz 2021-05-04 760 spin_lock_irq(&cma->lock);
dbe43d4d2837da Jaewon Kim 2017-02-24 761 pr_info("number of available pages: ");
c009da4258f988 Frank van der Linden 2025-02-28 762 for (r = 0; r < cma->nranges; r++) {
c009da4258f988 Frank van der Linden 2025-02-28 763 cmr = &cma->ranges[r];
c009da4258f988 Frank van der Linden 2025-02-28 764
c009da4258f988 Frank van der Linden 2025-02-28 765 nbits = cma_bitmap_maxno(cma, cmr);
c009da4258f988 Frank van der Linden 2025-02-28 766
c009da4258f988 Frank van der Linden 2025-02-28 767 pr_info("range %d: ", r);
77c50f9147eabc Yury Norov (NVIDIA 2025-07-19 @768) for_each_clear_bitrange(start, end, cmr->bitmap, nbits) {
77c50f9147eabc Yury Norov (NVIDIA 2025-07-19 769) nr_part = (end - start) << cma->order_per_bit;
77c50f9147eabc Yury Norov (NVIDIA 2025-07-19 @770) pr_cont("%s%lu@%lu", start ? "+" : "", nr_part, start);
dbe43d4d2837da Jaewon Kim 2017-02-24 771 }
c009da4258f988 Frank van der Linden 2025-02-28 772 pr_info("\n");
c009da4258f988 Frank van der Linden 2025-02-28 773 }
7365ff2c8eef4e Frank van der Linden 2025-02-28 774 pr_cont("=> %lu free of %lu total pages\n", cma->available_count,
7365ff2c8eef4e Frank van der Linden 2025-02-28 775 cma->count);
0ef7dcac998fef Mike Kravetz 2021-05-04 776 spin_unlock_irq(&cma->lock);
dbe43d4d2837da Jaewon Kim 2017-02-24 777 }
dbe43d4d2837da Jaewon Kim 2017-02-24 778
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-06-29 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 17:32 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-23 20:01 mm/cma.c:770:24-29: ERROR: iterator variable bound on line 768 cannot be NULL kernel test robot
2026-03-23 21:40 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=202606300158.lMSr2D6Z-lkp@intel.com \
--to=lkp@intel.com \
--cc=julia.lawall@inria.fr \
--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.