From: kernel test robot <lkp@intel.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>
Subject: [csky-linux:riscv_compat_v2_sv48_v3_mmind_pbmt 31/44] kernel/locking/locktorture.c:918:39: error: use of undeclared identifier '_PAGE_MTMASK'
Date: Wed, 19 Jan 2022 01:50:22 +0800 [thread overview]
Message-ID: <202201190125.dGN7taEZ-lkp@intel.com> (raw)
tree: https://github.com/c-sky/csky-linux riscv_compat_v2_sv48_v3_mmind_pbmt
head: b28a50c03a72c48d3895320bdd0757e0a8acb881
commit: a8a0c8f014166b1e95e223240632fd0baac50ea7 [31/44] hack in a debug output in freeinitmem
config: i386-randconfig-a002 (https://download.01.org/0day-ci/archive/20220119/202201190125.dGN7taEZ-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c10cbb243cafc0cf42c3e922cb29183279444432)
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
# https://github.com/c-sky/csky-linux/commit/a8a0c8f014166b1e95e223240632fd0baac50ea7
git remote add csky-linux https://github.com/c-sky/csky-linux
git fetch --no-tags csky-linux riscv_compat_v2_sv48_v3_mmind_pbmt
git checkout a8a0c8f014166b1e95e223240632fd0baac50ea7
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash kernel/locking/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> kernel/locking/locktorture.c:918:39: error: use of undeclared identifier '_PAGE_MTMASK'
printk("%s: -----> %llx\n", __func__, _PAGE_MTMASK);
^
1 error generated.
vim +/_PAGE_MTMASK +918 kernel/locking/locktorture.c
899
900 static int __init lock_torture_init(void)
901 {
902 int i, j;
903 int firsterr = 0;
904 static struct lock_torture_ops *torture_ops[] = {
905 &lock_busted_ops,
906 &spin_lock_ops, &spin_lock_irq_ops,
907 &rw_lock_ops, &rw_lock_irq_ops,
908 &mutex_lock_ops,
909 &ww_mutex_lock_ops,
910 #ifdef CONFIG_RT_MUTEXES
911 &rtmutex_lock_ops,
912 #endif
913 &rwsem_lock_ops,
914 &percpu_rwsem_lock_ops,
915 };
916
917
> 918 printk("%s: -----> %llx\n", __func__, _PAGE_MTMASK);
919
920
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-01-18 17:51 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=202201190125.dGN7taEZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=guoren@linux.alibaba.com \
--cc=heiko@sntech.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@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
Powered by JetHome