From: kernel test robot <lkp@intel.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: [bvanassche:block-bitwise-opf 15/15] block/blk-wbt.c:677:11: error: call to __compiletime_assert_332 declared with 'error' attribute: BUILD_BUG_ON failed: !__same_type(op, blk_mq_opf_t) && !__same_type(op, enum req_op)
Date: Fri, 17 Jun 2022 16:09:05 +0800 [thread overview]
Message-ID: <202206171642.Dj2zJ4rt-lkp@intel.com> (raw)
tree: https://github.com/bvanassche/linux block-bitwise-opf
head: 031ccdd616b11c4e774e56aa7eae906188ab24cc
commit: 031ccdd616b11c4e774e56aa7eae906188ab24cc [15/15] block: Introduce the type blk_mq_opf_t
config: hexagon-randconfig-r045-20220617 (https://download.01.org/0day-ci/archive/20220617/202206171642.Dj2zJ4rt-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project d764aa7fc6b9cc3fbe960019018f5f9e941eb0a6)
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/bvanassche/linux/commit/031ccdd616b11c4e774e56aa7eae906188ab24cc
git remote add bvanassche https://github.com/bvanassche/linux
git fetch --no-tags bvanassche block-bitwise-opf
git checkout 031ccdd616b11c4e774e56aa7eae906188ab24cc
# 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=hexagon SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> block/blk-wbt.c:677:11: error: call to __compiletime_assert_332 declared with 'error' attribute: BUILD_BUG_ON failed: !__same_type(op, blk_mq_opf_t) && !__same_type(op, enum req_op)
else if (op_is_write(op))
^
include/linux/blk_types.h:487:3: note: expanded from macro 'op_is_write'
BUILD_BUG_ON(!__same_type(op, blk_mq_opf_t) && \
^
include/linux/build_bug.h:50:2: note: expanded from macro 'BUILD_BUG_ON'
BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
^
include/linux/build_bug.h:39:37: note: expanded from macro 'BUILD_BUG_ON_MSG'
#define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
include/linux/compiler_types.h:340:2: note: expanded from macro '_compiletime_assert'
__compiletime_assert(condition, msg, prefix, suffix)
^
include/linux/compiler_types.h:333:4: note: expanded from macro '__compiletime_assert'
prefix ## suffix(); \
^
<scratch space>:89:1: note: expanded from here
__compiletime_assert_332
^
1 error generated.
vim +/error +677 block/blk-wbt.c
80e091d10e8bf7 Jens Axboe 2016-11-28 670
99c749a4c4f4ea Jens Axboe 2017-04-21 671 static int wbt_data_dir(const struct request *rq)
99c749a4c4f4ea Jens Axboe 2017-04-21 672 {
5235553d821433 Jens Axboe 2018-02-05 673 const int op = req_op(rq);
5235553d821433 Jens Axboe 2018-02-05 674
5235553d821433 Jens Axboe 2018-02-05 675 if (op == REQ_OP_READ)
5235553d821433 Jens Axboe 2018-02-05 676 return READ;
825843b0adb7c9 Jens Axboe 2018-05-03 @677 else if (op_is_write(op))
5235553d821433 Jens Axboe 2018-02-05 678 return WRITE;
5235553d821433 Jens Axboe 2018-02-05 679
5235553d821433 Jens Axboe 2018-02-05 680 /* don't account */
5235553d821433 Jens Axboe 2018-02-05 681 return -1;
99c749a4c4f4ea Jens Axboe 2017-04-21 682 }
99c749a4c4f4ea Jens Axboe 2017-04-21 683
:::::: The code at line 677 was first introduced by commit
:::::: 825843b0adb7c95e8cbab35e6fee64980e29ade8 blk-wbt: account any writing command as a write
:::::: TO: Jens Axboe <axboe@kernel.dk>
:::::: CC: Jens Axboe <axboe@kernel.dk>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-17 8:09 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=202206171642.Dj2zJ4rt-lkp@intel.com \
--to=lkp@intel.com \
--cc=bvanassche@acm.org \
--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