From: Keith Busch <kbusch@kernel.org>
To: Keith Busch <kbusch@meta.com>
Cc: hch@lst.de, martin.petersen@oracle.com,
linux-block@vger.kernel.org, axboe@devbig197.nha3.facebook.com
Subject: Re: [PATCH] blk-integrity: support bvec straddling block data
Date: Wed, 22 Oct 2025 19:32:30 -0600 [thread overview]
Message-ID: <aPmFroUdJkJCIjdo@kbusch-mbp> (raw)
In-Reply-To: <20251022235231.1334134-1-kbusch@meta.com>
On Wed, Oct 22, 2025 at 04:52:31PM -0700, Keith Busch wrote:
> @@ -65,48 +79,61 @@ static blk_status_t t10_pi_verify(struct blk_integrity_iter *iter,
> struct blk_integrity *bi)
> {
> u8 offset = bi->pi_offset;
> - unsigned int i;
> + unsigned int len, i;
> + bool skip = false;
>
> for (i = 0 ; i < iter->data_size ; i += iter->interval) {
Ooo, this should have been "i += len". I wrote some test cases to hit
that a bit after I sent this, so will need a v2. :(
next prev parent reply other threads:[~2025-10-23 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 23:52 [PATCH] blk-integrity: support bvec straddling block data Keith Busch
2025-10-23 1:32 ` Keith Busch [this message]
2025-10-23 8:22 ` Christoph Hellwig
2025-10-23 14:39 ` Keith Busch
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=aPmFroUdJkJCIjdo@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@devbig197.nha3.facebook.com \
--cc=hch@lst.de \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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