From: kernel test robot <lkp@intel.com>
To: Luis Chamberlain <mcgrof@do-not-panic.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [mcgrof:blk-iobuf-pool-v5 8/9] drivers/nvme/host/ioctl.c:668:8: error: call to undeclared function 'blk_uring_cmd_alloc_iobuf'; ISO C99 and later do not support implicit function declarations
Date: Tue, 28 Jul 2026 23:25:41 +0800 [thread overview]
Message-ID: <202607282300.TiDP3wkt-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git blk-iobuf-pool-v5
head: de80bacbf04a137715357b6a2948d9f29a18d990
commit: 7b61092440add7fbe6d72ae7ede11080113e193e [8/9] nvme: allocate pool-backed fixed buffers through namespace char devices
config: hexagon-randconfig-001-20260728 (https://download.01.org/0day-ci/archive/20260728/202607282300.TiDP3wkt-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 890b11e09e45e9d8b29f2f94f22052be3934e757)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260728/202607282300.TiDP3wkt-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/202607282300.TiDP3wkt-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/nvme/host/ioctl.c:668:8: error: call to undeclared function 'blk_uring_cmd_alloc_iobuf'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
668 | ret = blk_uring_cmd_alloc_iobuf(ioucmd, pool, buf_index, len,
| ^
1 error generated.
vim +/blk_uring_cmd_alloc_iobuf +668 drivers/nvme/host/ioctl.c
649
650 static int nvme_ns_alloc_iobuf(struct nvme_ns *ns, struct io_uring_cmd *ioucmd,
651 unsigned int issue_flags)
652 {
653 const struct io_uring_sqe *sqe = ioucmd->sqe;
654 struct blk_iobuf_pool *pool;
655 u64 buf_index, len;
656 int ret;
657
658 if (READ_ONCE(sqe->ioprio) || READ_ONCE(sqe->__pad1) ||
659 READ_ONCE(sqe->len) || READ_ONCE(sqe->rw_flags) ||
660 READ_ONCE(sqe->file_index))
661 return -EINVAL;
662 buf_index = READ_ONCE(sqe->addr);
663 len = READ_ONCE(sqe->addr3);
664
665 pool = blk_queue_get_iobuf_pool(ns->queue);
666 if (!pool)
667 return -EOPNOTSUPP;
> 668 ret = blk_uring_cmd_alloc_iobuf(ioucmd, pool, buf_index, len,
669 issue_flags);
670 blk_iobuf_pool_put(pool);
671 return ret;
672 }
673
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-07-28 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 15:25 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-28 1:39 [mcgrof:blk-iobuf-pool-v5 8/9] drivers/nvme/host/ioctl.c:668:8: error: call to undeclared function 'blk_uring_cmd_alloc_iobuf'; ISO C99 and later do not support implicit function declarations 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=202607282300.TiDP3wkt-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mcgrof@do-not-panic.com \
--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.