From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [sashal-linux-stable:queue-5.11 229/232] arch/arm64/mm/mmu.c:1466:13: error: implicit declaration of function 'mhp_range_allowed'
Date: Sun, 28 Mar 2021 10:33:08 +0800 [thread overview]
Message-ID: <202103281002.dE6JOrkZ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3576 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git queue-5.11
head: 3b2ab18cde84f27eb274d36d0272253af2cba3ed
commit: 6022ac619055d64c19b184ac845caa3345b39e1f [229/232] arm64/mm: define arch_get_mappable_range()
config: arm64-randconfig-r034-20210328 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project d3e7ee36f6411f1bb30ce31311131095d3a196c5)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git/commit/?id=6022ac619055d64c19b184ac845caa3345b39e1f
git remote add sashal-linux-stable https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git
git fetch --no-tags sashal-linux-stable queue-5.11
git checkout 6022ac619055d64c19b184ac845caa3345b39e1f
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
>> arch/arm64/mm/mmu.c:1446:14: warning: no previous prototype for function 'arch_get_mappable_range' [-Wmissing-prototypes]
struct range arch_get_mappable_range(void)
^
arch/arm64/mm/mmu.c:1446:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
struct range arch_get_mappable_range(void)
^
static
>> arch/arm64/mm/mmu.c:1466:13: error: implicit declaration of function 'mhp_range_allowed' [-Werror,-Wimplicit-function-declaration]
VM_BUG_ON(!mhp_range_allowed(start, size, true));
^
1 warning and 1 error generated.
vim +/mhp_range_allowed +1466 arch/arm64/mm/mmu.c
1445
> 1446 struct range arch_get_mappable_range(void)
1447 {
1448 struct range mhp_range;
1449
1450 /*
1451 * Linear mapping region is the range [PAGE_OFFSET..(PAGE_END - 1)]
1452 * accommodating both its ends but excluding PAGE_END. Max physical
1453 * range which can be mapped inside this linear mapping range, must
1454 * also be derived from its end points.
1455 */
1456 mhp_range.start = __pa(_PAGE_OFFSET(vabits_actual));
1457 mhp_range.end = __pa(PAGE_END - 1);
1458 return mhp_range;
1459 }
1460
1461 int arch_add_memory(int nid, u64 start, u64 size,
1462 struct mhp_params *params)
1463 {
1464 int ret, flags = 0;
1465
> 1466 VM_BUG_ON(!mhp_range_allowed(start, size, true));
1467 if (rodata_full || debug_pagealloc_enabled())
1468 flags = NO_BLOCK_MAPPINGS | NO_CONT_MAPPINGS;
1469
1470 __create_pgd_mapping(swapper_pg_dir, start, __phys_to_virt(start),
1471 size, params->pgprot, __pgd_pgtable_alloc,
1472 flags);
1473
1474 memblock_clear_nomap(start, size);
1475
1476 ret = __add_pages(nid, start >> PAGE_SHIFT, size >> PAGE_SHIFT,
1477 params);
1478 if (ret)
1479 __remove_pgd_mapping(swapper_pg_dir,
1480 __phys_to_virt(start), size);
1481 return ret;
1482 }
1483
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 26927 bytes --]
reply other threads:[~2021-03-28 2:33 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=202103281002.dE6JOrkZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.