dm-crypt: don't mess with BIP_BLOCK_INTEGRITY
authorChristoph Hellwig <hch@lst.de>
Wed, 9 Aug 2017 15:48:09 +0000 (17:48 +0200)
committerJens Axboe <axboe@kernel.dk>
Wed, 9 Aug 2017 16:00:31 +0000 (10:00 -0600)
This flag is never set right after calling bio_integrity_alloc,
so don't clear it and confuse the reader.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
drivers/md/dm-crypt.c

index cdf6b1e124604b7bd5e2fee7743a9435f1e79032..73c2e270cda61113c9e43600368ddfc99b4fd639 100644 (file)
@@ -933,9 +933,6 @@ static int dm_crypt_integrity_io_alloc(struct dm_crypt_io *io, struct bio *bio)
        bip->bip_iter.bi_size = tag_len;
        bip->bip_iter.bi_sector = io->cc->start + io->sector;
 
-       /* We own the metadata, do not let bio_free to release it */
-       bip->bip_flags &= ~BIP_BLOCK_INTEGRITY;
-
        ret = bio_integrity_add_page(bio, virt_to_page(io->integrity_metadata),
                                     tag_len, offset_in_page(io->integrity_metadata));
        if (unlikely(ret != tag_len))