From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [hch-misc:block-error-injection 3/7] block/blk-core.c:545:45: error: 'BD_MAKE_IT_FAIL' undeclared
Date: Mon, 01 Jun 2026 03:55:51 +0800 [thread overview]
Message-ID: <202606010341.ZynlUP5R-lkp@intel.com> (raw)
tree: git://git.infradead.org/users/hch/misc.git block-error-injection
head: f7d922716d709e96c39fc2a0ebc67eac84deb06d
commit: 31905bce1e3e0c7d6b853dc916a0f64fdec2673e [3/7] block: refactor should_fail_bio and should_fail_request
config: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20260601/202606010341.ZynlUP5R-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260601/202606010341.ZynlUP5R-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606010341.ZynlUP5R-lkp@intel.com/
All errors (new ones prefixed by >>):
block/blk-core.c: In function 'may_fail_bio':
>> block/blk-core.c:545:45: error: 'BD_MAKE_IT_FAIL' undeclared (first use in this function)
545 | return bdev_test_flag(bio->bi_bdev, BD_MAKE_IT_FAIL) ||
| ^~~~~~~~~~~~~~~
block/blk-core.c:545:45: note: each undeclared identifier is reported only once for each function it appears in
vim +/BD_MAKE_IT_FAIL +545 block/blk-core.c
540
541 static inline bool may_fail_bio(struct bio *bio)
542 {
543 if (!IS_ENABLED(CONFIG_FAIL_MAKE_REQUEST))
544 return false;
> 545 return bdev_test_flag(bio->bi_bdev, BD_MAKE_IT_FAIL) ||
546 (bio_flagged(bio, BIO_REMAPPED) &&
547 bdev_test_flag(bdev_whole(bio->bi_bdev), BD_MAKE_IT_FAIL));
548 }
549
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-31 19:56 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=202606010341.ZynlUP5R-lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=oe-kbuild-all@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 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.