From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@meta.com>
Cc: linux-block@vger.kernel.org, hch@lst.de,
linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCHv2] block: always allocate integrity buffer
Date: Thu, 8 May 2025 07:12:33 +0200 [thread overview]
Message-ID: <20250508051233.GA27118@lst.de> (raw)
In-Reply-To: <20250507191424.2436350-1-kbusch@meta.com>
On Wed, May 07, 2025 at 12:14:24PM -0700, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> The integrity buffer, whether or not you want it generated or verified, is
> mandatory for nvme formats that have metadata. The block integrity attributes
> read_verify and write_generate had been stopping the metadata buffer from being
This commit log exceeds the 73 characters allocated to it, please reformat
it.
> allocated and attached to the bio entirely. We only want to suppress the
> protection checks on the device and host, but we still need the buffer.
>
> Otherwise, reads and writes will just get IO errors and this nvme warning:
But to a point - the metadata buffer is only required for non-PI
metadata. I think from looking at the code that is exactly what
this patch does, but the commit log sounds different.
Also this should probably have a fixes tag.
> - if (bio_op(bio) == REQ_OP_READ && !bio->bi_status && bi->csum_type) {
> + if (bio_op(bio) == REQ_OP_READ && !bio->bi_status &&
> + bip->bip_flags & BIP_CHECK_GUARD) {
While Martin correctly points out we currently always do both guard
and reftag checking, we really should check for either, especially as
some code below is written in a way to allow for formats that only
have one of them.
> +static inline void bio_set_bip_flags(struct blk_integrity *bi, u16 *bip_flags)
> +{
> + if (bi->csum_type == BLK_INTEGRITY_CSUM_IP)
> + *bip_flags |= BIP_IP_CHECKSUM;
> + if (bi->csum_type)
> + *bip_flags |= BIP_CHECK_GUARD;
> + if (bi->flags & BLK_INTEGRITY_REF_TAG)
> + *bip_flags |= BIP_CHECK_REFTAG;
> +
Just return the flags here instead of the somewhat odd output by
pointer return?
> + break;
> + bio_set_bip_flags(bi, &bip_flags);
> break;
> case REQ_OP_WRITE:
...
> + bio_set_bip_flags(bi, &bip_flags);
> break;
> default:
> return true;
> @@ -134,22 +148,15 @@ bool bio_integrity_prep(struct bio *bio)
Just move this after the switch to have a single callsite. And maybe
don't even bother with the helper then?
next prev parent reply other threads:[~2025-05-08 5:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 19:14 [PATCHv2] block: always allocate integrity buffer Keith Busch
2025-05-07 22:31 ` Martin K. Petersen
2025-05-08 5:15 ` Christoph Hellwig
2025-05-08 5:12 ` Christoph Hellwig [this message]
2025-05-08 16:14 ` Keith Busch
2025-05-08 16:19 ` Christoph Hellwig
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=20250508051233.GA27118@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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