[dm-devel] [dm:for-next 30/32] drivers/md/dm-bio-record.h:45:7: error: 'struct bio' has no member named 'bi_integrity'; did you mean 'bi_iter'?

kbuild test robot lkp at intel.com
Sat Feb 29 07:45:30 UTC 2020


tree:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
head:   8a71e3cd0499fd9bfe1a99cda6a62fe83f80d622
commit: 6e18585702772969431c269438cb828a5e3d9db6 [30/32] dm bio record: save/restore bi_integrity and bi_end_io
config: x86_64-defconfig (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
        git checkout 6e18585702772969431c269438cb828a5e3d9db6
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp at intel.com>

All errors (new ones prefixed by >>):

   In file included from drivers/md/dm-raid1.c:8:0:
   drivers/md/dm-bio-record.h: In function 'dm_bio_restore':
>> drivers/md/dm-bio-record.h:45:7: error: 'struct bio' has no member named 'bi_integrity'; did you mean 'bi_iter'?
     bio->bi_integrity = bd->bi_integrity;
          ^~~~~~~~~~~~
          bi_iter

vim +45 drivers/md/dm-bio-record.h

    38	
    39	static inline void dm_bio_restore(struct dm_bio_details *bd, struct bio *bio)
    40	{
    41		bio->bi_disk = bd->bi_disk;
    42		bio->bi_partno = bd->bi_partno;
    43		bio->bi_flags = bd->bi_flags;
    44		bio->bi_iter = bd->bi_iter;
  > 45		bio->bi_integrity = bd->bi_integrity;
    46		if (bio->bi_end_io != bd->bi_end_io) {
    47			/* BIO_CHAIN may have been used, reset __bi_remaining */
    48			atomic_set(&bio->__bi_remaining, 1);
    49			bio->bi_end_io = bd->bi_end_io;
    50		}
    51	}
    52	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 28831 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/dm-devel/attachments/20200229/b0f8fb90/attachment.gz>


More information about the dm-devel mailing list