From: kernel test robot <lkp@intel.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH] ubd: add io_uring based userspace block driver
Date: Tue, 10 May 2022 20:00:49 +0800 [thread overview]
Message-ID: <202205101918.YlbroRMh-lkp@intel.com> (raw)
In-Reply-To: <20220509092312.254354-1-ming.lei@redhat.com>
Hi Ming,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on axboe-block/for-next]
[also build test ERROR on linux/master linus/master v5.18-rc6 next-20220509]
[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/intel-lab-lkp/linux/commits/Ming-Lei/ubd-add-io_uring-based-userspace-block-driver/20220509-173452
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: x86_64-randconfig-a003-20220509 (https://download.01.org/0day-ci/archive/20220510/202205101918.YlbroRMh-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project a385645b470e2d3a1534aae618ea56b31177639f)
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/intel-lab-lkp/linux/commit/898085c9876d078827ba8b3447e5d1ae4626d092
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Ming-Lei/ubd-add-io_uring-based-userspace-block-driver/20220509-173452
git checkout 898085c9876d078827ba8b3447e5d1ae4626d092
# save the config file
mkdir build_dir && cp config build_dir/.config
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 errors (new ones prefixed by >>):
In file included from <built-in>:1:
>> ./usr/include/linux/ubd_cmd.h:69:2: error: unknown type name '__u16'
__u16 nr_hw_queues;
^
./usr/include/linux/ubd_cmd.h:70:2: error: unknown type name '__u16'
__u16 queue_depth;
^
./usr/include/linux/ubd_cmd.h:71:2: error: unknown type name '__u16'
__u16 block_size;
^
./usr/include/linux/ubd_cmd.h:72:2: error: unknown type name '__u16'
__u16 state;
^
>> ./usr/include/linux/ubd_cmd.h:74:2: error: unknown type name '__u32'
__u32 rq_max_blocks;
^
./usr/include/linux/ubd_cmd.h:75:2: error: unknown type name '__u32'
__u32 dev_id;
^
>> ./usr/include/linux/ubd_cmd.h:77:2: error: unknown type name '__u64'
__u64 dev_blocks;
^
./usr/include/linux/ubd_cmd.h:78:2: error: unknown type name '__u64'
__u64 flags;
^
./usr/include/linux/ubd_cmd.h:87:2: error: unknown type name '__u64'
__u64 addr;
^
./usr/include/linux/ubd_cmd.h:88:2: error: unknown type name '__u32'
__u32 len;
^
>> ./usr/include/linux/ubd_cmd.h:89:2: error: unknown type name '__s32'
__s32 ubdsrv_pid;
^
./usr/include/linux/ubd_cmd.h:90:2: error: unknown type name '__u64'
__u64 reserved0[2];
^
./usr/include/linux/ubd_cmd.h:119:2: error: unknown type name '__u32'
__u32 op_flags;
^
./usr/include/linux/ubd_cmd.h:126:2: error: unknown type name '__u32'
__u32 tag_blocks;
^
./usr/include/linux/ubd_cmd.h:129:2: error: unknown type name '__u64'
__u64 start_block;
^
./usr/include/linux/ubd_cmd.h:132:2: error: unknown type name '__u64'
__u64 addr;
^
>> ./usr/include/linux/ubd_cmd.h:135:19: error: unknown type name '__u8'
static __inline__ __u8 ubdsrv_get_op(const struct ubdsrv_io_desc *iod)
^
./usr/include/linux/ubd_cmd.h:140:19: error: unknown type name '__u32'
static __inline__ __u32 ubdsrv_get_flags(const struct ubdsrv_io_desc *iod)
^
./usr/include/linux/ubd_cmd.h:145:19: error: unknown type name '__u32'
static __inline__ __u32 ubdsrv_get_blocks(const struct ubdsrv_io_desc *iod)
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-05-10 12:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 9:23 [RFC PATCH] ubd: add io_uring based userspace block driver Ming Lei
2022-05-09 15:10 ` Gabriel Krisman Bertazi
2022-05-10 1:57 ` Ming Lei
2022-05-10 4:22 ` Ziyang Zhang
2022-05-09 16:00 ` Randy Dunlap
2022-05-09 18:11 ` Gabriel Krisman Bertazi
2022-05-09 18:13 ` Jens Axboe
2022-05-09 16:09 ` Jens Axboe
2022-05-10 2:58 ` Ming Lei
2022-05-10 3:29 ` Jens Axboe
2022-05-10 7:38 ` Ming Lei
2022-05-09 18:14 ` Martin Raiber
2022-05-10 12:00 ` kernel test robot [this message]
2022-05-16 19:29 ` Stefan Hajnoczi
2022-05-17 1:57 ` Ming Lei
2022-05-17 6:17 ` Stefan Hajnoczi
2022-05-30 7:07 ` Pavel Machek
2022-06-02 3:19 ` Ming Lei
2022-06-06 2:15 ` Gao Xiang
2022-05-10 4:09 kernel test robot
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=202205101918.YlbroRMh-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@lists.linux.dev \
--cc=ming.lei@redhat.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 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.