From: kernel test robot <lkp@intel.com>
To: Sang-Heon Jeon <ekffu200098@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH] mm/hugetlb_cma: round up per_node before logging it
Date: Wed, 29 Apr 2026 07:23:34 +0800 [thread overview]
Message-ID: <202604290752.kPjM1Hkb-lkp@intel.com> (raw)
In-Reply-To: <20260421230220.4122996-1-ekffu200098@gmail.com>
Hi Sang-Heon,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on v7.0]
[also build test ERROR on linus/master]
[cannot apply to akpm-mm/mm-everything next-20260428]
[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/Sang-Heon-Jeon/mm-hugetlb_cma-round-up-per_node-before-logging-it/20260427-012923
base: v7.0
patch link: https://lore.kernel.org/r/20260421230220.4122996-1-ekffu200098%40gmail.com
patch subject: [RFC PATCH] mm/hugetlb_cma: round up per_node before logging it
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20260429/202604290752.kPjM1Hkb-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260429/202604290752.kPjM1Hkb-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/202604290752.kPjM1Hkb-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/asm-generic/bug.h:31,
from arch/x86/include/asm/bug.h:193,
from include/linux/bug.h:5,
from include/linux/mmdebug.h:5,
from include/linux/mm.h:7,
from mm/hugetlb_cma.c:3:
mm/hugetlb_cma.c: In function 'hugetlb_cma_reserve':
>> include/linux/printk.h:481:10: error: expected expression before '{' token
481 | ({ \
| ^
include/linux/printk.h:511:26: note: in expansion of macro 'printk_index_wrap'
511 | #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
| ^~~~~~~~~~~~~~~~~
include/linux/printk.h:584:9: note: in expansion of macro 'printk'
584 | printk(KERN_INFO pr_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~
mm/hugetlb_cma.c:208:17: note: in expansion of macro 'pr_info'
208 | pr_info("hugetlb_cma: reserve %lu MiB, up to %lu MiB per node\n",
| ^~~~~~~
In file included from include/linux/math64.h:6,
from include/linux/time64.h:5,
from include/linux/restart_block.h:9,
from include/linux/thread_info.h:14,
from include/linux/spinlock.h:60,
from include/linux/mmzone.h:8,
from include/linux/gfp.h:7,
from include/linux/mm.h:8:
>> include/linux/math.h:25:55: error: called object is not a function or function pointer
25 | #define round_up(x, y) ((((x)-1) | __round_mask(x, y))+1)
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
mm/hugetlb_cma.c:207:28: note: in expansion of macro 'round_up'
207 | per_node = round_up(per_node, PAGE_SIZE << order)
| ^~~~~~~~
vim +481 include/linux/printk.h
337015573718b1 Chris Down 2021-06-15 459
337015573718b1 Chris Down 2021-06-15 460 /*
337015573718b1 Chris Down 2021-06-15 461 * Some subsystems have their own custom printk that applies a va_format to a
337015573718b1 Chris Down 2021-06-15 462 * generic format, for example, to include a device number or other metadata
337015573718b1 Chris Down 2021-06-15 463 * alongside the format supplied by the caller.
337015573718b1 Chris Down 2021-06-15 464 *
337015573718b1 Chris Down 2021-06-15 465 * In order to store these in the way they would be emitted by the printk
337015573718b1 Chris Down 2021-06-15 466 * infrastructure, the subsystem provides us with the start, fixed string, and
337015573718b1 Chris Down 2021-06-15 467 * any subsequent text in the format string.
337015573718b1 Chris Down 2021-06-15 468 *
337015573718b1 Chris Down 2021-06-15 469 * We take a variable argument list as pr_fmt/dev_fmt/etc are sometimes passed
337015573718b1 Chris Down 2021-06-15 470 * as multiple arguments (eg: `"%s: ", "blah"`), and we must only take the
337015573718b1 Chris Down 2021-06-15 471 * first one.
337015573718b1 Chris Down 2021-06-15 472 *
337015573718b1 Chris Down 2021-06-15 473 * subsys_fmt_prefix must be known at compile time, or compilation will fail
337015573718b1 Chris Down 2021-06-15 474 * (since this is a mistake). If fmt or level is not known at compile time, no
337015573718b1 Chris Down 2021-06-15 475 * index entry will be made (since this can legitimately happen).
337015573718b1 Chris Down 2021-06-15 476 */
337015573718b1 Chris Down 2021-06-15 477 #define printk_index_subsys_emit(subsys_fmt_prefix, level, fmt, ...) \
337015573718b1 Chris Down 2021-06-15 478 __printk_index_emit(fmt, level, subsys_fmt_prefix)
337015573718b1 Chris Down 2021-06-15 479
337015573718b1 Chris Down 2021-06-15 480 #define printk_index_wrap(_p_func, _fmt, ...) \
337015573718b1 Chris Down 2021-06-15 @481 ({ \
337015573718b1 Chris Down 2021-06-15 482 __printk_index_emit(_fmt, NULL, NULL); \
337015573718b1 Chris Down 2021-06-15 483 _p_func(_fmt, ##__VA_ARGS__); \
337015573718b1 Chris Down 2021-06-15 484 })
337015573718b1 Chris Down 2021-06-15 485
337015573718b1 Chris Down 2021-06-15 486
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-04-28 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 23:02 [RFC PATCH] mm/hugetlb_cma: round up per_node before logging it Sang-Heon Jeon
2026-04-22 6:20 ` Muchun Song
2026-04-22 9:49 ` Sang-Heon Jeon
2026-04-28 11:57 ` kernel test robot
2026-04-28 23:23 ` 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=202604290752.kPjM1Hkb-lkp@intel.com \
--to=lkp@intel.com \
--cc=ekffu200098@gmail.com \
--cc=oe-kbuild-all@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.