From: kernel test robot <lkp@intel.com>
To: Keith Busch <kbusch@meta.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev, hch@lst.de,
axboe@kernel.dk, joshi.k@samsung.com,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv4 6/8] blk-mq-dma: add support for mapping integrity metadata
Date: Sun, 3 Aug 2025 07:11:29 +0800 [thread overview]
Message-ID: <202508030710.X3P9snty-lkp@intel.com> (raw)
In-Reply-To: <20250731150513.220395-7-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 linus/master next-20250801]
[cannot apply to linux-nvme/for-next hch-configfs/for-next v6.16]
[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/blk-mq-dma-introduce-blk_map_iter/20250731-230719
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
patch link: https://lore.kernel.org/r/20250731150513.220395-7-kbusch%40meta.com
patch subject: [PATCHv4 6/8] blk-mq-dma: add support for mapping integrity metadata
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20250803/202508030710.X3P9snty-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250803/202508030710.X3P9snty-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/202508030710.X3P9snty-lkp@intel.com/
All errors (new ones prefixed by >>):
>> block/blk-mq-dma.c:18:27: error: no member named 'bi_integrity' in 'struct bio'
18 | iter->iter = iter->bio->bi_integrity->bip_iter;
| ~~~~~~~~~ ^
block/blk-mq-dma.c:19:27: error: no member named 'bi_integrity' in 'struct bio'
19 | iter->bvec = iter->bio->bi_integrity->bip_vec;
| ~~~~~~~~~ ^
2 errors generated.
vim +18 block/blk-mq-dma.c
8
9 static bool __blk_map_iter_next(struct blk_map_iter *iter)
10 {
11 if (iter->iter.bi_size)
12 return true;
13 if (!iter->bio || !iter->bio->bi_next)
14 return false;
15
16 iter->bio = iter->bio->bi_next;
17 if (iter->is_integrity) {
> 18 iter->iter = iter->bio->bi_integrity->bip_iter;
19 iter->bvec = iter->bio->bi_integrity->bip_vec;
20 } else {
21 iter->iter = iter->bio->bi_iter;
22 iter->bvec = iter->bio->bi_io_vec;
23 }
24 return true;
25 }
26
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-02 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 15:05 [PATCHv4 0/8] blk-mq: introduce blk_map_iter Keith Busch
2025-07-31 15:05 ` [PATCHv4 1/8] blk-mq-dma: " Keith Busch
2025-07-31 15:05 ` [PATCHv4 2/8] blk-mq-dma: provide the bio_vec list being iterated Keith Busch
2025-07-31 15:05 ` [PATCHv4 3/8] blk-mq-dma: require unmap caller provide p2p map type Keith Busch
2025-07-31 15:05 ` [PATCHv4 4/8] blk-mq: remove REQ_P2PDMA flag Keith Busch
2025-08-08 12:54 ` Kanchan Joshi
2025-07-31 15:05 ` [PATCHv4 5/8] blk-mq-dma: move common dma start code to a helper Keith Busch
2025-07-31 15:05 ` [PATCHv4 6/8] blk-mq-dma: add support for mapping integrity metadata Keith Busch
2025-08-02 23:11 ` kernel test robot [this message]
2025-07-31 15:05 ` [PATCHv4 7/8] nvme-pci: create common sgl unmapping helper Keith Busch
2025-07-31 15:05 ` [PATCHv4 8/8] nvme-pci: convert metadata mapping to dma iter Keith Busch
2025-08-08 13:01 ` Kanchan Joshi
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=202508030710.X3P9snty-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=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--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