From: kernel test robot <lkp@intel.com>
To: Keith Busch <kbusch@meta.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 2/5] block: add support for copy offload
Date: Thu, 22 May 2025 18:04:09 +0800 [thread overview]
Message-ID: <202505221702.EcgNFozB-lkp@intel.com> (raw)
In-Reply-To: <20250521223107.709131-3-kbusch@meta.com>
Hi Keith,
kernel test robot noticed the following build warnings:
[auto build test WARNING on axboe-block/for-next]
[also build test WARNING on next-20250521]
[cannot apply to linux-nvme/for-next brauner-vfs/vfs.all linus/master v6.15-rc7]
[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/block-new-sector-copy-api/20250522-063316
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
patch link: https://lore.kernel.org/r/20250521223107.709131-3-kbusch%40meta.com
patch subject: [PATCH 2/5] block: add support for copy offload
config: x86_64-buildonly-randconfig-001-20250522 (https://download.01.org/0day-ci/archive/20250522/202505221702.EcgNFozB-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250522/202505221702.EcgNFozB-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/202505221702.EcgNFozB-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> block/blk-integrity.c:29:31: warning: suggest braces around initialization of subobject [-Wmissing-braces]
29 | struct bio_vec iv, ivprv = { NULL };
| ^~~~
| { }
include/linux/stddef.h:8:14: note: expanded from macro 'NULL'
8 | #define NULL ((void *)0)
| ^~~~~~~~~~~
block/blk-integrity.c:69:31: warning: suggest braces around initialization of subobject [-Wmissing-braces]
69 | struct bio_vec iv, ivprv = { NULL };
| ^~~~
| { }
include/linux/stddef.h:8:14: note: expanded from macro 'NULL'
8 | #define NULL ((void *)0)
| ^~~~~~~~~~~
2 warnings generated.
vim +29 block/blk-integrity.c
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 18
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 19 /**
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 20 * blk_rq_count_integrity_sg - Count number of integrity scatterlist elements
13f05c8d8e98bb Martin K. Petersen 2010-09-10 21 * @q: request queue
13f05c8d8e98bb Martin K. Petersen 2010-09-10 22 * @bio: bio with integrity metadata attached
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 23 *
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 24 * Description: Returns the number of elements required in a
13f05c8d8e98bb Martin K. Petersen 2010-09-10 25 * scatterlist corresponding to the integrity metadata in a bio.
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 26 */
13f05c8d8e98bb Martin K. Petersen 2010-09-10 27 int blk_rq_count_integrity_sg(struct request_queue *q, struct bio *bio)
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 28 {
d57a5f7c6605f1 Kent Overstreet 2013-11-23 @29 struct bio_vec iv, ivprv = { NULL };
13f05c8d8e98bb Martin K. Petersen 2010-09-10 30 unsigned int segments = 0;
13f05c8d8e98bb Martin K. Petersen 2010-09-10 31 unsigned int seg_size = 0;
d57a5f7c6605f1 Kent Overstreet 2013-11-23 32 struct bvec_iter iter;
d57a5f7c6605f1 Kent Overstreet 2013-11-23 33 int prev = 0;
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 34
d57a5f7c6605f1 Kent Overstreet 2013-11-23 35 bio_for_each_integrity_vec(iv, bio, iter) {
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 36
d57a5f7c6605f1 Kent Overstreet 2013-11-23 37 if (prev) {
3dccdae54fe836 Christoph Hellwig 2018-09-24 38 if (!biovec_phys_mergeable(q, &ivprv, &iv))
13f05c8d8e98bb Martin K. Petersen 2010-09-10 39 goto new_segment;
d57a5f7c6605f1 Kent Overstreet 2013-11-23 40 if (seg_size + iv.bv_len > queue_max_segment_size(q))
13f05c8d8e98bb Martin K. Petersen 2010-09-10 41 goto new_segment;
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 42
d57a5f7c6605f1 Kent Overstreet 2013-11-23 43 seg_size += iv.bv_len;
13f05c8d8e98bb Martin K. Petersen 2010-09-10 44 } else {
13f05c8d8e98bb Martin K. Petersen 2010-09-10 45 new_segment:
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 46 segments++;
d57a5f7c6605f1 Kent Overstreet 2013-11-23 47 seg_size = iv.bv_len;
13f05c8d8e98bb Martin K. Petersen 2010-09-10 48 }
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 49
d57a5f7c6605f1 Kent Overstreet 2013-11-23 50 prev = 1;
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 51 ivprv = iv;
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 52 }
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 53
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 54 return segments;
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 55 }
7ba1ba12eeef0a Martin K. Petersen 2008-06-30 56
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-22 10:04 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 22:31 [PATCH 0/5] block: another block copy offload Keith Busch
2025-05-21 22:31 ` [PATCH 1/5] block: new sector copy api Keith Busch
2025-05-22 10:02 ` Hannes Reinecke
2025-05-22 16:43 ` Keith Busch
2025-05-22 19:22 ` Bart Van Assche
2025-05-22 20:04 ` Keith Busch
2025-05-23 12:45 ` Christoph Hellwig
2025-05-23 17:02 ` Keith Busch
2025-05-26 5:18 ` Christoph Hellwig
2025-05-27 17:45 ` Keith Busch
2025-05-28 7:46 ` Christoph Hellwig
2025-05-28 22:41 ` Keith Busch
2025-06-02 4:58 ` Christoph Hellwig
2025-05-21 22:31 ` [PATCH 2/5] block: add support for copy offload Keith Busch
2025-05-22 10:04 ` kernel test robot [this message]
2025-05-22 13:49 ` Hannes Reinecke
2025-05-23 12:46 ` Christoph Hellwig
2025-05-23 13:26 ` Keith Busch
2025-05-23 13:37 ` Christoph Hellwig
2025-05-23 13:48 ` Keith Busch
2025-05-26 5:22 ` Christoph Hellwig
2025-05-27 21:33 ` Keith Busch
2025-05-28 7:47 ` Christoph Hellwig
2025-05-21 22:31 ` [PATCH 3/5] nvme: " Keith Busch
2025-05-22 0:47 ` Caleb Sander Mateos
2025-05-22 0:51 ` Caleb Sander Mateos
2025-05-22 3:23 ` Keith Busch
2025-05-22 3:41 ` Caleb Sander Mateos
2025-05-22 4:29 ` Keith Busch
2025-05-22 14:16 ` Caleb Sander Mateos
2025-05-23 12:49 ` Christoph Hellwig
2025-05-23 12:48 ` Christoph Hellwig
2025-05-22 13:54 ` Hannes Reinecke
2025-05-23 12:50 ` Christoph Hellwig
2025-05-23 14:22 ` Caleb Sander Mateos
2025-06-09 9:29 ` Niklas Cassel
2025-05-21 22:31 ` [PATCH 4/5] block: add support for vectored copies Keith Busch
2025-05-22 9:33 ` kernel test robot
2025-05-22 13:58 ` Hannes Reinecke
2025-05-22 16:36 ` Keith Busch
2025-05-21 22:31 ` [PATCH 5/5] nvmet: implement copy support for bdev backed target Keith Busch
2025-05-22 12:51 ` kernel test robot
2025-05-22 13:59 ` Hannes Reinecke
2025-05-23 13:18 ` Christoph Hellwig
2025-05-23 14:00 ` Keith Busch
2025-05-23 14:02 ` Christoph Hellwig
2025-05-22 15:52 ` [PATCH 0/5] block: another block copy offload Bart Van Assche
2025-05-23 12:53 ` Christoph Hellwig
2025-07-03 14:47 ` Niklas Cassel
-- strict thread matches above, loose matches on Subject: below --
2025-05-22 12:51 [PATCH 2/5] block: add support for " kernel test robot
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=202505221702.EcgNFozB-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbusch@meta.com \
--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 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.