All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [mcgrof:blk-iobuf-pool-v5-premap-iova 13/14] drivers/nvme/host/ioctl.c:136:14: error: call to undeclared function 'io_uring_cmd_kbuf_priv'; ISO C99 and later do not support implicit function declarations
Date: Mon, 17 Aug 2026 01:09:30 +0800	[thread overview]
Message-ID: <202608170020.N3auIDXR-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git blk-iobuf-pool-v5-premap-iova
head:   912328a605c4767433d483436a2d592d06063095
commit: 77b944e2c92e23c377117a624ac22fa2d37fe877 [13/14] nvme: issue premapped commands past the dma_opt clamp
config: hexagon-randconfig-r113-20260816 (https://download.01.org/0day-ci/archive/20260817/202608170020.N3auIDXR-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 844a18e753e822736c9805ab779144b647a2c186)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260817/202608170020.N3auIDXR-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/202608170020.N3auIDXR-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/nvme/host/ioctl.c:136:14: error: call to undeclared function 'io_uring_cmd_kbuf_priv'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     136 |         kbuf_priv = io_uring_cmd_kbuf_priv(ioucmd, issue_flags);
         |                     ^
>> drivers/nvme/host/ioctl.c:136:12: error: incompatible integer to pointer conversion assigning to 'void *' from 'int' [-Wint-conversion]
     136 |         kbuf_priv = io_uring_cmd_kbuf_priv(ioucmd, issue_flags);
         |                   ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   2 errors generated.


vim +/io_uring_cmd_kbuf_priv +136 drivers/nvme/host/ioctl.c

   125	
   126	static void nvme_setup_premapped(struct request *req, struct nvme_ns *ns,
   127					 struct io_uring_cmd *ioucmd,
   128					 unsigned int issue_flags)
   129	{
   130	#ifdef CONFIG_BLK_IOBUF_POOL
   131		struct blk_dma_premap *premap;
   132		void *kbuf_priv;
   133	
   134		if (!ioucmd)
   135			return;
 > 136		kbuf_priv = io_uring_cmd_kbuf_priv(ioucmd, issue_flags);
   137		if (!kbuf_priv)
   138			return;
   139		premap = blk_iobuf_fixed_buf_premap(kbuf_priv, ns->ctrl->dev);
   140		if (!premap)
   141			return;
   142		/*
   143		 * The buffer is persistently mapped to our DMA device. Record the
   144		 * retained mapping BEFORE the buffer is mapped into the request, so
   145		 * blk_rq_map_user_bvec sizes the gate on max_hw_premapped_sectors rather
   146		 * than the 128K dma_opt clamp; req->dma_premap on the request is the sole
   147		 * marker of a premapped request from here on.
   148		 */
   149		req->dma_premap = premap;
   150	#endif
   151	}
   152	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-08-16 17:10 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=202608170020.N3auIDXR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=mcgrof@kernel.org \
    --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.