From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>, Song Liu <song@kernel.org>,
Yu Kuai <yukuai3@huawei.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Kanchan Joshi <joshi.k@samsung.com>,
linux-block@vger.kernel.org, dm-devel@lists.linux.dev,
linux-raid@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH 2/3] block: move the block layer auto-integrity code into a new file
Date: Wed, 19 Feb 2025 17:37:25 +0100 [thread overview]
Message-ID: <1858bc0a-465b-4cf3-a95c-dbe05740adff@suse.de> (raw)
In-Reply-To: <20250218182207.3982214-3-hch@lst.de>
On 2/18/25 19:21, Christoph Hellwig wrote:
> The code that automatically creates a integrity payload and generates /
> verifies the checksums for bios that don't have submitter-provided
> integrity payload currently sits right in the middle of the block
> integrity metadata infrastruture. Split it into a separate file to
> make the different layers clear.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> block/Makefile | 3 +-
> block/bio-integrity-auto.c | 162 +++++++++++++++++++++++++++++++++++++
> block/bio-integrity.c | 159 ------------------------------------
> 3 files changed, 164 insertions(+), 160 deletions(-)
> create mode 100644 block/bio-integrity-auto.c
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2025-02-19 16:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 18:21 split out the auto-PI code and data structures Christoph Hellwig
2025-02-18 18:21 ` [PATCH 1/3] block: mark bounce buffering as incompatible with integrity Christoph Hellwig
2025-02-18 18:30 ` Johannes Thumshirn
2025-02-19 16:35 ` Hannes Reinecke
2025-02-21 6:04 ` Anuj gupta
2025-02-18 18:21 ` [PATCH 2/3] block: move the block layer auto-integrity code into a new file Christoph Hellwig
2025-02-18 18:28 ` Johannes Thumshirn
2025-02-19 1:35 ` Martin K. Petersen
2025-02-19 11:33 ` Kanchan Joshi
2025-02-19 16:37 ` Hannes Reinecke [this message]
2025-02-21 6:04 ` Anuj gupta
2025-02-18 18:21 ` [PATCH 3/3] block: split struct bio_integrity_data Christoph Hellwig
2025-02-19 11:34 ` Kanchan Joshi
2025-02-19 16:40 ` Hannes Reinecke
2025-02-21 6:07 ` Anuj gupta
-- strict thread matches above, loose matches on Subject: below --
2025-02-25 15:44 split out the auto-PI code and data structures v2 Christoph Hellwig
2025-02-25 15:44 ` [PATCH 2/3] block: move the block layer auto-integrity code into a new file Christoph Hellwig
2025-01-31 12:24 RFC: split out the auto-PI code and data structures Christoph Hellwig
2025-01-31 12:24 ` [PATCH 2/3] block: move the block layer auto-integrity code into a new file Christoph Hellwig
2025-02-03 19:41 ` Martin K. Petersen
2025-02-04 5:45 ` 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=1858bc0a-465b-4cf3-a95c-dbe05740adff@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=target-devel@vger.kernel.org \
--cc=yukuai3@huawei.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;
as well as URLs for NNTP newsgroup(s).