From: kernel test robot <lkp@intel.com>
To: Chuck Lever <cel@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC 7/9] DMA: Add dma_map_bvecs_attrs()
Date: Fri, 20 Oct 2023 06:10:37 +0800 [thread overview]
Message-ID: <202310200655.lcp1jrR1-lkp@intel.com> (raw)
In-Reply-To: <169772917833.5232.13488378553385610086.stgit@klimt.1015granger.net>
Hi Chuck,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on rdma/for-next linus/master v6.6-rc6 next-20231019]
[cannot apply to joro-iommu/next]
[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/Chuck-Lever/dma-debug-Fix-a-typo-in-a-debugging-eye-catcher/20231020-032859
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/169772917833.5232.13488378553385610086.stgit%40klimt.1015granger.net
patch subject: [PATCH RFC 7/9] DMA: Add dma_map_bvecs_attrs()
config: loongarch-allyesconfig (https://download.01.org/0day-ci/archive/20231020/202310200655.lcp1jrR1-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231020/202310200655.lcp1jrR1-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/202310200655.lcp1jrR1-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/dma/mapping.c:321: warning: expecting prototype for dma_map_sg_attrs(). Prototype was for dma_map_bvecs_attrs() instead
vim +321 kernel/dma/mapping.c
298
299 /**
300 * dma_map_sg_attrs - Map the given buffer for DMA
301 * @dev: The device for which to perform the DMA operation
302 * @bvecs: The bio_vec array describing the buffer
303 * @nents: Number of bio_vecs to map
304 * @dir: DMA direction
305 * @attrs: Optional DMA attributes for the map operation
306 *
307 * Maps a buffer described by a bio_vec array passed in the bvecs
308 * argument with nents segments for the @dir DMA operation by the
309 * @dev device.
310 *
311 * Returns the number of mapped entries (which can be less than nents)
312 * on success. Zero is returned for any error.
313 *
314 * dma_unmap_bvecs_attrs() should be used to unmap the buffer with the
315 * original bvecs and original nents (not the value returned by this
316 * function).
317 */
318 unsigned int dma_map_bvecs_attrs(struct device *dev, struct bio_vec *bvecs,
319 int nents, enum dma_data_direction dir,
320 unsigned long attrs)
> 321 {
322 const struct dma_map_ops *ops = get_dma_ops(dev);
323 int ents;
324
325 BUG_ON(!valid_dma_direction(dir));
326
327 if (WARN_ON_ONCE(!dev->dma_mask))
328 return 0;
329
330 if (dma_map_direct(dev, ops))
331 ents = dma_direct_map_bvecs(dev, bvecs, nents, dir, attrs);
332 else
333 ents = ops->map_bvecs(dev, bvecs, nents, dir, attrs);
334
335 if (ents > 0) {
336 kmsan_handle_dma_bvecs(bvecs, nents, dir);
337 debug_dma_map_bvecs(dev, bvecs, nents, ents, dir, attrs);
338 } else if (WARN_ON_ONCE(ents != -EINVAL && ents != -ENOMEM &&
339 ents != -EIO && ents != -EREMOTEIO)) {
340 return -EIO;
341 }
342
343 return ents;
344 }
345 EXPORT_SYMBOL_GPL(dma_map_bvecs_attrs);
346
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-19 22:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 15:25 [PATCH RFC 0/9] Exploring biovec support in (R)DMA API Chuck Lever
2023-10-19 15:25 ` Chuck Lever
2023-10-19 15:25 ` [PATCH RFC 1/9] dma-debug: Fix a typo in a debugging eye-catcher Chuck Lever
2023-10-20 4:49 ` Christoph Hellwig
2023-10-20 13:38 ` Chuck Lever III
2023-10-23 5:56 ` Christoph Hellwig
2023-10-19 15:25 ` [PATCH RFC 2/9] bvec: Add bio_vec fields to manage DMA mapping Chuck Lever
2023-10-19 15:25 ` Chuck Lever
2023-10-19 15:25 ` [PATCH RFC 3/9] dma-debug: Add dma_debug_ helpers for mapping bio_vec arrays Chuck Lever
2023-10-19 15:25 ` Chuck Lever
2023-10-19 21:38 ` kernel test robot
2023-10-19 23:21 ` Chuck Lever III
2023-10-23 2:43 ` Liu, Yujie
2023-10-23 14:27 ` Chuck Lever III
2023-10-19 21:49 ` kernel test robot
2023-10-19 15:25 ` [PATCH RFC 4/9] mm: kmsan: Add support for DMA " Chuck Lever
2023-10-19 15:25 ` Chuck Lever
2023-10-19 15:26 ` [PATCH RFC 5/9] dma-direct: Support direct " Chuck Lever
2023-10-19 15:26 ` Chuck Lever
2023-10-19 15:26 ` [PATCH RFC 6/9] DMA-API: Add dma_sync_bvecs_for_cpu() and dma_sync_bvecs_for_device() Chuck Lever
2023-10-19 15:26 ` Chuck Lever
2023-10-19 15:26 ` [PATCH RFC 7/9] DMA: Add dma_map_bvecs_attrs() Chuck Lever
2023-10-19 15:26 ` Chuck Lever
2023-10-19 22:10 ` kernel test robot [this message]
2023-10-19 15:26 ` [PATCH RFC 8/9] iommu/dma: Support DMA-mapping a bio_vec array Chuck Lever
2023-10-19 15:26 ` Chuck Lever
2023-10-19 15:26 ` [PATCH RFC 9/9] RDMA: Add helpers for DMA-mapping an array of bio_vecs Chuck Lever
2023-10-19 15:26 ` Chuck Lever
2023-10-19 15:53 ` [PATCH RFC 0/9] Exploring biovec support in (R)DMA API Matthew Wilcox
2023-10-19 17:48 ` Chuck Lever
2023-10-20 4:58 ` Christoph Hellwig
2023-10-20 10:30 ` Robin Murphy
2023-10-23 5:59 ` Christoph Hellwig
2023-10-19 16:43 ` Robin Murphy
2023-10-19 17:53 ` Jason Gunthorpe
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=202310200655.lcp1jrR1-lkp@intel.com \
--to=lkp@intel.com \
--cc=cel@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.