From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android12-5.10 7519/10554] userfaultfd.c:373:44: error: expected ')' before 'PRIx64'
Date: Tue, 13 Jul 2021 01:51:34 +0800 [thread overview]
Message-ID: <202107130129.k6gpUXhs-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4108 bytes --]
Hi Axel,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android12-5.10
head: 2742be5903724a4db0fe1df2624bba18311c0f5f
commit: 357700fcc3b51b66e2a790c5bb036d97916086af [7519/10554] FROMGIT: userfaultfd/selftests: add test exercising minor fault handling
config: x86_64-rhel-8.3-kselftests (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
git remote add android-common https://android.googlesource.com/kernel/common
git fetch --no-tags android-common android12-5.10
git checkout 357700fcc3b51b66e2a790c5bb036d97916086af
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash -C tools/testing/selftests/vm install
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 >>):
userfaultfd.c: In function 'continue_range':
>> userfaultfd.c:373:44: error: expected ')' before 'PRIx64'
373 | "UFFDIO_CONTINUE failed for address 0x%" PRIx64 "\n",
| ^~~~~~~
| )
userfaultfd.c:373:42: warning: spurious trailing '%' in format [-Wformat=]
373 | "UFFDIO_CONTINUE failed for address 0x%" PRIx64 "\n",
| ^
userfaultfd.c: In function 'uffd_handle_page_fault':
>> userfaultfd.c:597:3: error: unknown type name 'uint8_t'; did you mean 'u_int8_t'?
597 | uint8_t *area;
| ^~~~~~~
| u_int8_t
>> userfaultfd.c:612:11: error: 'uint8_t' undeclared (first use in this function); did you mean 'u_int8_t'?
612 | area = (uint8_t *)(area_dst +
| ^~~~~~~
| u_int8_t
userfaultfd.c:612:11: note: each undeclared identifier is reported only once for each function it appears in
>> userfaultfd.c:612:20: error: expected expression before ')' token
612 | area = (uint8_t *)(area_dst +
| ^
userfaultfd.c: At top level:
>> userfaultfd.c:827:33: error: unknown type name 'uint64_t'; did you mean 'u_int64_t'?
827 | static int userfaultfd_open_ext(uint64_t *features)
| ^~~~~~~~
| u_int64_t
userfaultfd.c:854:29: error: unknown type name 'uint64_t'; did you mean 'u_int64_t'?
854 | static int userfaultfd_open(uint64_t features)
| ^~~~~~~~
| u_int64_t
userfaultfd.c: In function 'userfaultfd_zeropage_test':
userfaultfd.c:1097:6: warning: implicit declaration of function 'userfaultfd_open' [-Wimplicit-function-declaration]
1097 | if (userfaultfd_open(0) < 0)
| ^~~~~~~~~~~~~~~~
userfaultfd.c: In function 'userfaultfd_minor_test':
userfaultfd.c:1288:2: error: unknown type name 'uint8_t'; did you mean 'u_int8_t'?
1288 | uint8_t expected_byte;
| ^~~~~~~
| u_int8_t
userfaultfd.c:1292:2: error: unknown type name 'uint64_t'; did you mean 'u_int64_t'?
1292 | uint64_t features = UFFD_FEATURE_MINOR_HUGETLBFS;
| ^~~~~~~~
| u_int64_t
userfaultfd.c:1303:6: warning: implicit declaration of function 'userfaultfd_open_ext'; did you mean 'userfaultfd_sig_test'? [-Wimplicit-function-declaration]
1303 | if (userfaultfd_open_ext(&features))
| ^~~~~~~~~~~~~~~~~~~~
| userfaultfd_sig_test
userfaultfd.c:1332:44: error: 'uint8_t' undeclared (first use in this function); did you mean 'u_int8_t'?
1332 | memset(area_dst + (p * page_size), p % ((uint8_t)-1),
| ^~~~~~~
| u_int8_t
---
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: 41712 bytes --]
reply other threads:[~2021-07-12 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=202107130129.k6gpUXhs-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.