From: kernel test robot <lkp@intel.com>
To: Keith Busch <kbusch@meta.com>,
hch@lst.de, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
axboe@kernel.dk, leon@kernel.org, joshi.k@samsung.com,
sagi@grimberg.me, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH 1/2] blk-integrity: add scatter-less DMA mapping helpers
Date: Thu, 26 Jun 2025 21:55:27 +0800 [thread overview]
Message-ID: <202506262136.WXl2reWF-lkp@intel.com> (raw)
In-Reply-To: <20250625204445.1802483-1-kbusch@meta.com>
Hi Keith,
kernel test robot noticed the following build errors:
[auto build test ERROR on axboe-block/for-next]
[also build test ERROR on next-20250626]
[cannot apply to linux-nvme/for-next hch-configfs/for-next linus/master v6.16-rc3]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Keith-Busch/nvme-convert-metadata-mapping-to-dma-iter/20250626-044623
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
patch link: https://lore.kernel.org/r/20250625204445.1802483-1-kbusch%40meta.com
patch subject: [PATCH 1/2] blk-integrity: add scatter-less DMA mapping helpers
config: x86_64-buildonly-randconfig-002-20250626 (https://download.01.org/0day-ci/archive/20250626/202506262136.WXl2reWF-lkp@intel.com/config)
compiler: clang version 20.1.7 (https://github.com/llvm/llvm-project 6146a88f60492b520a36f8f8f3231e15f3cc6082)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250626/202506262136.WXl2reWF-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/202506262136.WXl2reWF-lkp@intel.com/
All errors (new ones prefixed by >>):
>> block/blk-integrity.c:194:19: error: use of undeclared identifier 'blk_rq_integrity_map_iter_start'
194 | EXPORT_SYMBOL_GPL(blk_rq_integrity_map_iter_start);
| ^
1 error generated.
vim +/blk_rq_integrity_map_iter_start +194 block/blk-integrity.c
165
166 bool blk_rq_integrity_dma_map_iter_start(struct request *req,
167 struct device *dma_dev, struct blk_dma_iter *iter)
168 {
169 struct bio_integrity_payload *bip = bio_integrity(req->bio);
170 struct phys_vec vec;
171
172 iter->iter.bio = req->bio;
173 iter->iter.iter = bip->bip_iter;
174 memset(&iter->p2pdma, 0, sizeof(iter->p2pdma));
175 iter->status = BLK_STS_OK;
176
177 if (!blk_rq_integrity_map_iter_next(req, &iter->iter, &vec))
178 return false;
179
180 switch (pci_p2pdma_state(&iter->p2pdma, dma_dev,
181 phys_to_page(vec.paddr))) {
182 case PCI_P2PDMA_MAP_BUS_ADDR:
183 return blk_dma_map_bus(iter, &vec);
184 case PCI_P2PDMA_MAP_THRU_HOST_BRIDGE:
185 case PCI_P2PDMA_MAP_NONE:
186 break;
187 default:
188 iter->status = BLK_STS_INVAL;
189 return false;
190 }
191
192 return blk_dma_map_direct(req, dma_dev, iter, &vec);
193 }
> 194 EXPORT_SYMBOL_GPL(blk_rq_integrity_map_iter_start);
195
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-06-26 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 20:44 [PATCH 1/2] blk-integrity: add scatter-less DMA mapping helpers Keith Busch
2025-06-25 20:44 ` [PATCH 2/2] nvme: convert metadata mapping to dma iter Keith Busch
2025-06-25 21:18 ` Keith Busch
2025-06-26 5:11 ` Christoph Hellwig
2025-06-26 13:55 ` kernel test robot
2025-06-25 21:17 ` [PATCH 1/2] blk-integrity: add scatter-less DMA mapping helpers Keith Busch
2025-06-26 5:02 ` Christoph Hellwig
2025-06-26 13:55 ` kernel test robot [this message]
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=202506262136.WXl2reWF-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=leon@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sagi@grimberg.me \
/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.