From: kernel test robot <lkp@intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [mcgrof:blk-iobuf-pool-v5-premap-iova 12/14] Warning: block/blk-mq-dma.c:235 cannot understand function prototype: '/* * Premapped path: the buffer is persistently DMA-mapped as one contiguous IOVA * (dma_iova_*), so hand the whole mapping to the iterator as a single segment * instead of allocati...
Date: Fri, 31 Jul 2026 07:56:52 +0200 [thread overview]
Message-ID: <202607310722.zfznlplf-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: ca011e66fdccef93bc916c7cf32323ad7b6fe2e2 [12/14] block, io_uring: premap a pool buffer to exceed the dma_opt clamp
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260731/202607310722.zfznlplf-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260731/202607310722.zfznlplf-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/202607310722.zfznlplf-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: block/blk-mq-dma.c:235 cannot understand function prototype: '/* * Premapped path: the buffer is persistently DMA-mapped as one contiguous IOVA * (dma_iova_*), so hand the whole mapping to the iterator as a single segment * instead of allocating an IOVA per I/O. This is what lets a premapped request * exceed the dma_opt_mapping_size() clamp folded into max_hw_sectors. The * completion path must NOT unmap it (see nvme_unmap_data). * * NOTE: this emits the mapping from its start, i.e. it assumes the request * covers the buffer from offset 0. The whole-buffer fixed-buffer command path * used by the pool selftest satisfies that; an arbitrary buffer offset needs'
Warning: block/blk-mq-dma.c:430 Excess function parameter 'state' description in 'blk_rq_integrity_dma_map_iter_next'
Warning: block/blk-mq-dma.c:430 Excess function parameter 'state' description in 'blk_rq_integrity_dma_map_iter_next'
--
Warning: block/blk-map.c:366 Excess function parameter 'op' description in 'bio_copy_kern'
>> Warning: block/blk-map.c:516 function parameter 'opts' not described in 'blk_rq_map_user_iov_opts'
>> Warning: block/blk-map.c:516 expecting prototype for blk_rq_map_user_iov(). Prototype was for blk_rq_map_user_iov_opts() instead
Warning: block/blk-map.c:366 Excess function parameter 'op' description in 'bio_copy_kern'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-31 5: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=202607310722.zfznlplf-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox