From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [hch-block:blkdev.h-includes 15/16] block/keyslot-manager.c:442:6: error: implicit declaration of function 'blk_integrity_queue_supports_integrity'
Date: Sun, 25 Jul 2021 04:29:15 +0800 [thread overview]
Message-ID: <202107250408.ieamDIH5-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3019 bytes --]
tree: git://git.infradead.org/users/hch/block.git blkdev.h-includes
head: 48f7fda047613ceec07881f14a5eaf1ee19d4433
commit: e7a8094f7da3b6e7c7a853afa0dd9d7e40fafff2 [15/16] block: move integrity handling out of blkdev.h
config: i386-randconfig-a005-20210724 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce (this is a W=1 build):
git remote add hch-block git://git.infradead.org/users/hch/block.git
git fetch --no-tags hch-block blkdev.h-includes
git checkout e7a8094f7da3b6e7c7a853afa0dd9d7e40fafff2
# save the attached .config to linux build tree
make W=1 ARCH=i386
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 >>):
block/keyslot-manager.c: In function 'blk_ksm_register':
>> block/keyslot-manager.c:442:6: error: implicit declaration of function 'blk_integrity_queue_supports_integrity' [-Werror=implicit-function-declaration]
442 | if (blk_integrity_queue_supports_integrity(q)) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from include/linux/blkdev.h:7,
from include/linux/blk-crypto.h:72,
from include/linux/keyslot-manager.h:10,
from block/keyslot-manager.c:31:
At top level:
include/linux/genhd.h:329:12: warning: 'bd_register_pending_holders' defined but not used [-Wunused-function]
329 | static int bd_register_pending_holders(struct gendisk *disk)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/blk_integrity_queue_supports_integrity +442 block/keyslot-manager.c
d145dc23030bbf Satya Tangirala 2020-05-14 439
d145dc23030bbf Satya Tangirala 2020-05-14 440 bool blk_ksm_register(struct blk_keyslot_manager *ksm, struct request_queue *q)
d145dc23030bbf Satya Tangirala 2020-05-14 441 {
d145dc23030bbf Satya Tangirala 2020-05-14 @442 if (blk_integrity_queue_supports_integrity(q)) {
d145dc23030bbf Satya Tangirala 2020-05-14 443 pr_warn("Integrity and hardware inline encryption are not supported together. Disabling hardware inline encryption.\n");
d145dc23030bbf Satya Tangirala 2020-05-14 444 return false;
d145dc23030bbf Satya Tangirala 2020-05-14 445 }
d145dc23030bbf Satya Tangirala 2020-05-14 446 q->ksm = ksm;
d145dc23030bbf Satya Tangirala 2020-05-14 447 return true;
d145dc23030bbf Satya Tangirala 2020-05-14 448 }
d145dc23030bbf Satya Tangirala 2020-05-14 449 EXPORT_SYMBOL_GPL(blk_ksm_register);
d145dc23030bbf Satya Tangirala 2020-05-14 450
:::::: The code at line 442 was first introduced by commit
:::::: d145dc23030bbf2de3a8ca5e0c29c2e568f69737 block: Make blk-integrity preclude hardware inline encryption
:::::: TO: Satya Tangirala <satyat@google.com>
:::::: CC: Jens Axboe <axboe@kernel.dk>
---
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: 31209 bytes --]
reply other threads:[~2021-07-24 20:45 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=202107250408.ieamDIH5-lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).