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,
tglx@linutronix.de, arnd@arndb.de, namhyung@kernel.org,
peterz@infradead.org, alistair23@gmail.com, jolsa@redhat.com,
dave@stgolabs.net, mingo@redhat.com, dvhart@infradead.org
Subject: Re: [PATCH v3 3/6] uapi: futex: Add a futex syscall
Date: Sat, 27 Nov 2021 16:41:19 +0800 [thread overview]
Message-ID: <202111271634.gZ4ePXuJ-lkp@intel.com> (raw)
In-Reply-To: <20211126060024.3290177-3-alistair.francis@opensource.wdc.com>
Hi Alistair,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/locking/core]
[also build test ERROR on linux/master soc/for-next linus/master v5.16-rc2 next-20211126]
[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/perf-bench-futex-Add-support-for-32-bit-systems-with-64-bit-time_t/20211126-140752
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 3297481d688a5cc2973ea58bd78e66b8639748b1
config: x86_64-randconfig-a002-20211126 (https://download.01.org/0day-ci/archive/20211127/202111271634.gZ4ePXuJ-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 5162b558d8c0b542e752b037e72a69d5fd51eb1e)
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/e6bfd30ff20551d613ea63d17bc9667179a593de
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Alistair-Francis/perf-bench-futex-Add-support-for-32-bit-systems-with-64-bit-time_t/20211126-140752
git checkout e6bfd30ff20551d613ea63d17bc9667179a593de
# 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=x86_64 SHELL=/bin/bash
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 >>):
In file included from <built-in>:1:
>> ./usr/include/linux/futex_syscall.h:30:16: warning: declaration of 'struct timespec' will not be visible outside of this function [-Wvisibility]
struct timespec *timeout, __volatile__ uint32_t *uaddr2, int val3)
^
>> ./usr/include/linux/futex_syscall.h:42: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:30:16: note: forward declaration of 'struct timespec'
struct timespec *timeout, __volatile__ uint32_t *uaddr2, int val3)
^
>> ./usr/include/linux/futex_syscall.h:43: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:45:24: error: incomplete definition of type 'struct timespec'
if (timeout && timeout->tv_sec == (long)timeout->tv_sec) {
~~~~~~~^
./usr/include/linux/futex_syscall.h:30:16: note: forward declaration of 'struct timespec'
struct timespec *timeout, __volatile__ uint32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:45:49: error: incomplete definition of type 'struct timespec'
if (timeout && timeout->tv_sec == (long)timeout->tv_sec) {
~~~~~~~^
./usr/include/linux/futex_syscall.h:30:16: note: forward declaration of 'struct timespec'
struct timespec *timeout, __volatile__ uint32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:48:44: error: incomplete definition of type 'struct timespec'
ts_old.tv_sec = (__kernel_long_t) timeout->tv_sec;
~~~~~~~^
./usr/include/linux/futex_syscall.h:30:16: note: forward declaration of 'struct timespec'
struct timespec *timeout, __volatile__ uint32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:49:45: error: incomplete definition of type 'struct timespec'
ts_old.tv_nsec = (__kernel_long_t) timeout->tv_nsec;
~~~~~~~^
./usr/include/linux/futex_syscall.h:30:16: note: forward declaration of 'struct timespec'
struct timespec *timeout, __volatile__ uint32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:53:46: error: use of undeclared identifier 'NULL'
return syscall(__NR_futex, uaddr, op, val, NULL, uaddr2, val3);
^
./usr/include/linux/futex_syscall.h:82:9: error: implicit declaration of function 'syscall' [-Werror,-Wimplicit-function-declaration]
return syscall(__NR_futex, uaddr, op, val, nr_requeue, uaddr2, val3);
^
1 warning and 8 errors generated.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2021-11-27 8:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 6:00 [PATCH v3 1/6] perf bench futex: Add support for 32-bit systems with 64-bit time_t Alistair Francis
2021-11-26 6:00 ` [PATCH v3 2/6] selftests: futex: Call the futex syscall from a function Alistair Francis
2021-11-26 6:00 ` [PATCH v3 3/6] uapi: futex: Add a futex syscall Alistair Francis
2021-11-26 7:24 ` Arnd Bergmann
2021-11-27 8:41 ` kernel test robot [this message]
2021-11-26 6:00 ` [PATCH v3 4/6] selftests: futex: Add support for 32-bit systems with 64-bit time_t Alistair Francis
2021-11-26 7:36 ` Arnd Bergmann
2021-11-26 6:00 ` [PATCH v3 5/6] uapi: futex: Add a futex waitv syscall Alistair Francis
2021-11-26 7:27 ` Arnd Bergmann
2021-11-26 6:00 ` [PATCH v3 6/6] selftests: futex: Use futex_waitv helper function Alistair Francis
2021-11-26 7:33 ` Arnd Bergmann
2021-11-26 7:19 ` [PATCH v3 1/6] perf bench futex: Add support for 32-bit systems with 64-bit time_t Arnd Bergmann
2022-02-26 11:47 ` Arnaldo Carvalho de Melo
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=202111271634.gZ4ePXuJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=alistair.francis@opensource.wdc.com \
--cc=alistair23@gmail.com \
--cc=arnd@arndb.de \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=jolsa@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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