From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Lyashkov, Alexey" <alexey.lyashkov@hpe.com>
Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Jens Axboe <axboe@kernel.dk>,
Bart Van Assche <bvanassche@acm.org>,
"Dmitry Fomichev" <dmitry.fomichev@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 0/1] t10-pi bio split fix
Date: Thu, 13 Jan 2022 14:59:35 -0500 [thread overview]
Message-ID: <yq1k0f3pg4y.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <71B870D7-16B9-4299-ACB0-F4B6D5188C70@hpe.com> (Alexey Lyashkov's message of "Thu, 13 Jan 2022 11:13:36 +0000")
Alexey,
> Ping for review.
Can you please try the following patch?
--
Martin K. Petersen Oracle Linux Engineering
diff --git a/block/bio-integrity.c b/block/bio-integrity.c
index c0eb901315f9..fa5bc5b13c6a 100644
--- a/block/bio-integrity.c
+++ b/block/bio-integrity.c
@@ -387,7 +387,7 @@ void bio_integrity_advance(struct bio *bio, unsigned int bytes_done)
struct blk_integrity *bi = blk_get_integrity(bio->bi_disk);
unsigned bytes = bio_integrity_bytes(bi, bytes_done >> 9);
- bip->bip_iter.bi_sector += bytes_done >> 9;
+ bip->bip_iter.bi_sector += bio_integrity_intervals(bi, bytes_done >> 9);
bvec_iter_advance(bip->bip_vec, &bip->bip_iter, bytes);
}
next prev parent reply other threads:[~2022-01-13 19:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211220134422.1045336-1-alexey.lyashkov@hpe.com>
[not found] ` <yq1wnjzi6oc.fsf@ca-mkp.ca.oracle.com>
[not found] ` <82F812AE-BEFA-4F57-A134-C1EED7F1928E@hpe.com>
2021-12-30 2:23 ` [PATCH 0/1] t10-pi bio split fix Damien Le Moal
2022-01-13 11:13 ` Lyashkov, Alexey
2022-01-13 19:59 ` Martin K. Petersen [this message]
2022-01-14 12:25 ` Lyashkov, Alexey
2022-02-02 17:42 Ivanov, Dmitry (HPC)
2022-02-04 3:44 ` Martin K. Petersen
2022-02-04 7:43 ` Milan Broz
2022-02-04 7:58 ` Lyashkov, Alexey
2022-02-05 3:03 ` Ivanov, Dmitry (HPC)
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=yq1k0f3pg4y.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=alexey.lyashkov@hpe.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dmitry.fomichev@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).