From: kernel test robot <lkp@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [block:io_uring-fops.v7 6/8] fs/block_dev.c:344:10: error: implicit declaration of function 'blkdev_uring_ioctl'; did you mean 'blkdev_async_ioctl'?
Date: Thu, 9 Sep 2021 03:30:46 +0800 [thread overview]
Message-ID: <202109090340.cKQ1zpPB-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git io_uring-fops.v7
head: 733ce76b0107afe87534cfdd5403594ccef3bbe9
commit: e9640aeebe88d42bf792d7ad773498d7f001b453 [6/8] block: add example ioctl
config: um-x86_64_defconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?id=e9640aeebe88d42bf792d7ad773498d7f001b453
git remote add block https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
git fetch --no-tags block io_uring-fops.v7
git checkout e9640aeebe88d42bf792d7ad773498d7f001b453
# save the attached .config to linux build tree
make W=1 ARCH=um SUBARCH=x86_64
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 >>):
fs/block_dev.c: In function 'blkdev_async_cmd':
>> fs/block_dev.c:344:10: error: implicit declaration of function 'blkdev_uring_ioctl'; did you mean 'blkdev_async_ioctl'? [-Werror=implicit-function-declaration]
344 | return blkdev_uring_ioctl(bdev, cmd);
| ^~~~~~~~~~~~~~~~~~
| blkdev_async_ioctl
At top level:
fs/block_dev.c:324:12: warning: 'blkdev_async_ioctl' defined but not used [-Wunused-function]
324 | static int blkdev_async_ioctl(struct block_device *bdev,
| ^~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +344 fs/block_dev.c
336
337 static int blkdev_async_cmd(struct io_uring_cmd *cmd,
338 enum io_uring_cmd_flags flags)
339 {
340 struct block_device *bdev = I_BDEV(cmd->file->f_mapping->host);
341
342 switch (cmd->op) {
343 case BLOCK_URING_OP_IOCTL:
> 344 return blkdev_uring_ioctl(bdev, cmd);
345 default:
346 break;
347 }
348
349 return blk_uring_cmd(bdev, cmd, flags);
350 }
351
---
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: 9639 bytes --]
reply other threads:[~2021-09-08 19:31 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=202109090340.cKQ1zpPB-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--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
all inboxes | Powered by JetHome®