From: kernel test robot <lkp@intel.com>
To: Alistair Francis <alistair.francis@opensource.wdc.com>,
linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
alistair23@gmail.com, arnd@arndb.de,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH v2] uapi: futex: Add a futex syscall
Date: Thu, 21 Oct 2021 19:54:14 +0800 [thread overview]
Message-ID: <202110211945.82q0wt9m-lkp@intel.com> (raw)
In-Reply-To: <20211021055408.4006408-1-alistair.francis@opensource.wdc.com>
[-- Attachment #1: Type: text/plain, Size: 7394 bytes --]
Hi Alistair,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linux/master]
[also build test ERROR on soc/for-next linus/master v5.15-rc6 next-20211021]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Alistair-Francis/uapi-futex-Add-a-futex-syscall/20211021-135527
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2f111a6fd5b5297b4e92f53798ca086f7c7d33a4
config: i386-randconfig-a004-20211021 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 3cea2505fd8d99a9ba0cb625aecfe28a47c4e3f8)
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/0day-ci/linux/commit/6dcb960761dacb92295496cefad0a38e19d4c8ba
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Alistair-Francis/uapi-futex-Add-a-futex-syscall/20211021-135527
git checkout 6dcb960761dacb92295496cefad0a38e19d4c8ba
# save the attached .config 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
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 >>):
In file included from <built-in>:1:
./usr/include/linux/futex_syscall.h:21:45: error: unknown type name 'u_int32_t'
__kernel_futex_syscall_timeout(__volatile__ u_int32_t *uaddr, int op, u_int32_t val,
^
./usr/include/linux/futex_syscall.h:21:71: error: unknown type name 'u_int32_t'
__kernel_futex_syscall_timeout(__volatile__ u_int32_t *uaddr, int op, u_int32_t val,
^
./usr/include/linux/futex_syscall.h:22:16: warning: declaration of 'struct timespec' will not be visible outside of this function [-Wvisibility]
struct timespec *timeout, __volatile__ u_int32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:22:48: error: unknown type name 'u_int32_t'
struct timespec *timeout, __volatile__ u_int32_t *uaddr2, int val3)
^
>> ./usr/include/linux/futex_syscall.h:25:12: error: invalid application of 'sizeof' to an incomplete type 'struct timespec'
if (sizeof(*timeout) != sizeof(struct __kernel_old_timespec)) {
^~~~~~~~~~
./usr/include/linux/futex_syscall.h:22:16: note: forward declaration of 'struct timespec'
struct timespec *timeout, __volatile__ u_int32_t *uaddr2, int val3)
^
>> ./usr/include/linux/futex_syscall.h:26:14: error: implicit declaration of function 'syscall' [-Werror,-Wimplicit-function-declaration]
int ret = syscall(__NR_futex_time64, uaddr, op, val, timeout, uaddr2, val3);
^
./usr/include/linux/futex_syscall.h:34:12: error: invalid application of 'sizeof' to an incomplete type 'struct timespec'
if (sizeof(*timeout) == sizeof(struct __kernel_old_timespec))
^~~~~~~~~~
./usr/include/linux/futex_syscall.h:22:16: note: forward declaration of 'struct timespec'
struct timespec *timeout, __volatile__ u_int32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:35:10: error: implicit declaration of function 'syscall' [-Werror,-Wimplicit-function-declaration]
return syscall(__NR_futex, uaddr, op, val, timeout, uaddr2, val3);
^
>> ./usr/include/linux/futex_syscall.h:37:24: error: incomplete definition of type 'struct timespec'
if (timeout && timeout->tv_sec == (long)timeout->tv_sec) {
~~~~~~~^
./usr/include/linux/futex_syscall.h:22:16: note: forward declaration of 'struct timespec'
struct timespec *timeout, __volatile__ u_int32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:37:49: error: incomplete definition of type 'struct timespec'
if (timeout && timeout->tv_sec == (long)timeout->tv_sec) {
~~~~~~~^
./usr/include/linux/futex_syscall.h:22:16: note: forward declaration of 'struct timespec'
struct timespec *timeout, __volatile__ u_int32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:40:42: error: incomplete definition of type 'struct timespec'
ts32.tv_sec = (__kernel_long_t) timeout->tv_sec;
~~~~~~~^
./usr/include/linux/futex_syscall.h:22:16: note: forward declaration of 'struct timespec'
struct timespec *timeout, __volatile__ u_int32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:41:43: error: incomplete definition of type 'struct timespec'
ts32.tv_nsec = (__kernel_long_t) timeout->tv_nsec;
~~~~~~~^
./usr/include/linux/futex_syscall.h:22:16: note: forward declaration of 'struct timespec'
struct timespec *timeout, __volatile__ u_int32_t *uaddr2, int val3)
^
>> ./usr/include/linux/futex_syscall.h:45:46: error: use of undeclared identifier 'NULL'
return syscall(__NR_futex, uaddr, op, val, NULL, uaddr2, val3);
^
./usr/include/linux/futex_syscall.h:63:48: error: unknown type name 'u_int32_t'
__kernel_futex_syscall_nr_requeue(__volatile__ u_int32_t *uaddr, int op, u_int32_t val,
^
./usr/include/linux/futex_syscall.h:63:74: error: unknown type name 'u_int32_t'
__kernel_futex_syscall_nr_requeue(__volatile__ u_int32_t *uaddr, int op, u_int32_t val,
^
./usr/include/linux/futex_syscall.h:64:5: error: unknown type name 'u_int32_t'
u_int32_t nr_requeue, __volatile__ u_int32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:64:40: error: unknown type name 'u_int32_t'
u_int32_t nr_requeue, __volatile__ u_int32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:67:13: error: implicit declaration of function 'syscall' [-Werror,-Wimplicit-function-declaration]
int ret = syscall(__NR_futex_time64, uaddr, op, val, nr_requeue, uaddr2, val3);
^
1 warning and 17 errors generated.
---
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: 29370 bytes --]
next prev parent reply other threads:[~2021-10-21 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 5:54 [PATCH v2] uapi: futex: Add a futex syscall Alistair Francis
2021-10-21 6:30 ` Arnd Bergmann
2021-10-21 11:54 ` kernel test robot [this message]
2021-10-25 16:33 ` André Almeida
2021-10-25 17:32 ` Arnd Bergmann
2021-11-23 5:44 ` Alistair Francis
2021-11-24 6:10 ` Alistair Francis
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=202110211945.82q0wt9m-lkp@intel.com \
--to=lkp@intel.com \
--cc=alistair.francis@opensource.wdc.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=arnd@arndb.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