From: kbuild test robot <lkp@intel.com>
To: "Steven, Price," <steven.price@arm.com>
Cc: kbuild-all@lists.01.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 13212/14131] arch/riscv/mm/ptdump.c:255:17: error: initialization of 'void (*)(struct ptdump_state *, long unsigned int, int, u64)' {aka 'void (*)(struct ptdump_state *, long unsigned int, int, long long unsigned int)'} from incompatible pointer type 'void (*)(struct ptdump_state *, long unsigned int, int, long unsigned int)'
Date: Mon, 1 Jun 2020 06:43:14 +0800 [thread overview]
Message-ID: <202006010612.nhQJT2N3%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3515 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: e7b08814b16b80a0bf76eeca16317f8c2ed23b8c
commit: 8e1fbb89ffff1b66d68ad6f28b5dda689def97d9 [13212/14131] mm: ptdump: expand type of 'val' in note_page()
config: riscv-allyesconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.3.0
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
git checkout 8e1fbb89ffff1b66d68ad6f28b5dda689def97d9
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
arch/riscv/mm/ptdump.c: In function 'ptdump_walk':
>> arch/riscv/mm/ptdump.c:255:17: error: initialization of 'void (*)(struct ptdump_state *, long unsigned int, int, u64)' {aka 'void (*)(struct ptdump_state *, long unsigned int, int, long long unsigned int)'} from incompatible pointer type 'void (*)(struct ptdump_state *, long unsigned int, int, long unsigned int)' [-Werror=incompatible-pointer-types]
255 | .note_page = note_page,
| ^~~~~~~~~
arch/riscv/mm/ptdump.c:255:17: note: (near initialization for 'st.ptdump.note_page')
arch/riscv/mm/ptdump.c: In function 'ptdump_check_wx':
arch/riscv/mm/ptdump.c:277:17: error: initialization of 'void (*)(struct ptdump_state *, long unsigned int, int, u64)' {aka 'void (*)(struct ptdump_state *, long unsigned int, int, long long unsigned int)'} from incompatible pointer type 'void (*)(struct ptdump_state *, long unsigned int, int, long unsigned int)' [-Werror=incompatible-pointer-types]
277 | .note_page = note_page,
| ^~~~~~~~~
arch/riscv/mm/ptdump.c:277:17: note: (near initialization for 'st.ptdump.note_page')
cc1: some warnings being treated as errors
vim +255 arch/riscv/mm/ptdump.c
59c4da8640ccf4 Zong Li 2020-03-12 247
59c4da8640ccf4 Zong Li 2020-03-12 248 static void ptdump_walk(struct seq_file *s)
59c4da8640ccf4 Zong Li 2020-03-12 249 {
59c4da8640ccf4 Zong Li 2020-03-12 250 struct pg_state st = {
59c4da8640ccf4 Zong Li 2020-03-12 251 .seq = s,
59c4da8640ccf4 Zong Li 2020-03-12 252 .marker = address_markers,
59c4da8640ccf4 Zong Li 2020-03-12 253 .level = -1,
59c4da8640ccf4 Zong Li 2020-03-12 254 .ptdump = {
59c4da8640ccf4 Zong Li 2020-03-12 @255 .note_page = note_page,
59c4da8640ccf4 Zong Li 2020-03-12 256 .range = (struct ptdump_range[]) {
59c4da8640ccf4 Zong Li 2020-03-12 257 {KERN_VIRT_START, ULONG_MAX},
59c4da8640ccf4 Zong Li 2020-03-12 258 {0, 0}
59c4da8640ccf4 Zong Li 2020-03-12 259 }
59c4da8640ccf4 Zong Li 2020-03-12 260 }
59c4da8640ccf4 Zong Li 2020-03-12 261 };
59c4da8640ccf4 Zong Li 2020-03-12 262
59c4da8640ccf4 Zong Li 2020-03-12 263 ptdump_walk_pgd(&st.ptdump, &init_mm, NULL);
59c4da8640ccf4 Zong Li 2020-03-12 264 }
59c4da8640ccf4 Zong Li 2020-03-12 265
:::::: The code at line 255 was first introduced by commit
:::::: 59c4da8640ccf4721d54d36835706f3eefb521a4 riscv: Add support to dump the kernel page tables
:::::: TO: Zong Li <zong.li@sifive.com>
:::::: CC: Palmer Dabbelt <palmerdabbelt@google.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 63368 bytes --]
reply other threads:[~2020-05-31 22:43 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=202006010612.nhQJT2N3%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=steven.price@arm.com \
/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