From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 10352/10516] include/linux/mm.h:101:35: error: 'MAX_PHYSMEM_BITS' undeclared
Date: Tue, 10 Sep 2024 09:33:48 +0800 [thread overview]
Message-ID: <202409100913.RxkfrKU6-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 100cc857359b5d731407d1038f7e76cd0e871d94
commit: 5f445800cbdfc4b4185d496a43dfd78df63d2265 [10352/10516] Merge branch 'mm-everything' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20240910/202409100913.RxkfrKU6-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240910/202409100913.RxkfrKU6-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/202409100913.RxkfrKU6-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/ioport.h:15,
from kernel/resource.c:15:
kernel/resource.c: In function 'gfr_start':
>> include/linux/mm.h:101:35: error: 'MAX_PHYSMEM_BITS' undeclared (first use in this function)
101 | # define PHYSMEM_END ((1ULL << MAX_PHYSMEM_BITS) - 1)
| ^~~~~~~~~~~~~~~~
include/linux/minmax.h:93:38: note: in definition of macro '__cmp_once_unique'
93 | ({ type ux = (x); type uy = (y); __cmp(op, ux, uy); })
| ^
include/linux/minmax.h:213:27: note: in expansion of macro '__cmp_once'
213 | #define min_t(type, x, y) __cmp_once(min, type, x, y)
| ^~~~~~~~~~
kernel/resource.c:1874:23: note: in expansion of macro 'min_t'
1874 | end = min_t(resource_size_t, base->end, PHYSMEM_END);
| ^~~~~
kernel/resource.c:1874:57: note: in expansion of macro 'PHYSMEM_END'
1874 | end = min_t(resource_size_t, base->end, PHYSMEM_END);
| ^~~~~~~~~~~
include/linux/mm.h:101:35: note: each undeclared identifier is reported only once for each function it appears in
101 | # define PHYSMEM_END ((1ULL << MAX_PHYSMEM_BITS) - 1)
| ^~~~~~~~~~~~~~~~
include/linux/minmax.h:93:38: note: in definition of macro '__cmp_once_unique'
93 | ({ type ux = (x); type uy = (y); __cmp(op, ux, uy); })
| ^
include/linux/minmax.h:213:27: note: in expansion of macro '__cmp_once'
213 | #define min_t(type, x, y) __cmp_once(min, type, x, y)
| ^~~~~~~~~~
kernel/resource.c:1874:23: note: in expansion of macro 'min_t'
1874 | end = min_t(resource_size_t, base->end, PHYSMEM_END);
| ^~~~~
kernel/resource.c:1874:57: note: in expansion of macro 'PHYSMEM_END'
1874 | end = min_t(resource_size_t, base->end, PHYSMEM_END);
| ^~~~~~~~~~~
kernel/resource.c: In function 'gfr_continue':
>> include/linux/mm.h:101:35: error: 'MAX_PHYSMEM_BITS' undeclared (first use in this function)
101 | # define PHYSMEM_END ((1ULL << MAX_PHYSMEM_BITS) - 1)
| ^~~~~~~~~~~~~~~~
include/linux/minmax.h:93:38: note: in definition of macro '__cmp_once_unique'
93 | ({ type ux = (x); type uy = (y); __cmp(op, ux, uy); })
| ^
include/linux/minmax.h:213:27: note: in expansion of macro '__cmp_once'
213 | #define min_t(type, x, y) __cmp_once(min, type, x, y)
| ^~~~~~~~~~
kernel/resource.c:1891:24: note: in expansion of macro 'min_t'
1891 | addr <= min_t(resource_size_t, base->end, PHYSMEM_END);
| ^~~~~
kernel/resource.c:1891:58: note: in expansion of macro 'PHYSMEM_END'
1891 | addr <= min_t(resource_size_t, base->end, PHYSMEM_END);
| ^~~~~~~~~~~
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for GET_FREE_REGION
Depends on [n]: SPARSEMEM [=n]
Selected by [m]:
- RESOURCE_KUNIT_TEST [=m] && RUNTIME_TESTING_MENU [=y] && KUNIT [=m]
vim +/MAX_PHYSMEM_BITS +101 include/linux/mm.h
d07e22597d1d35 Daniel Cashman 2016-01-14 99
ea72ce5da22806 Thomas Gleixner 2024-08-14 100 #ifndef PHYSMEM_END
ea72ce5da22806 Thomas Gleixner 2024-08-14 @101 # define PHYSMEM_END ((1ULL << MAX_PHYSMEM_BITS) - 1)
ea72ce5da22806 Thomas Gleixner 2024-08-14 102 #endif
ea72ce5da22806 Thomas Gleixner 2024-08-14 103
:::::: The code at line 101 was first introduced by commit
:::::: ea72ce5da22806d5713f3ffb39a6d5ae73841f93 x86/kaslr: Expose and use the end of the physical memory address space
:::::: TO: Thomas Gleixner <tglx@linutronix.de>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-09-10 1:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 1:33 kernel test robot [this message]
2024-09-10 3:45 ` Andrew Morton
2024-09-10 5:42 ` Huang, Ying
2024-09-10 17:40 ` Andrew Morton
2024-09-11 1:06 ` Huang, Ying
2024-09-11 2:32 ` Stephen Rothwell
2024-09-11 3:45 ` Andrew Morton
2024-09-11 5:18 ` Huang, Ying
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=202409100913.RxkfrKU6-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox