From: Harald Freudenberger <freude@linux.ibm.com>
To: dengler@linux.ibm.com, ifranzki@linux.ibm.com, agk@redhat.com,
snitzer@kernel.org, mpatocka@redhat.com
Cc: linux-s390@vger.kernel.org, dm-devel@lists.linux.dev,
herbert@gondor.apana.org.au
Subject: [PATCH v2 0/2] dm-integrity: Implement asynch digest support
Date: Wed, 29 Jan 2025 17:25:26 +0100 [thread overview]
Message-ID: <20250129162528.57124-1-freude@linux.ibm.com> (raw)
Support for ahashes in dm-integrity.
Please note this code is elementary tested but needs some more
test coverage before integration. I can't do that as I only have
a s390 platform but I assume someone from dmcrypt/dmintegrity will
run a more sophisticated test suite on this.
Changelog:
v1: First implementation. Tested with crc32, sha256, hmac-sha256 and
the s390 specific implementations for hmac-sha256 and protected
key phmac-sha256. Also ran with some instrumented code (in the digest
implementation) to verify that in fact now the code runs asynchronous.
v2: Support shash and ahash. Based on Mikulas' idea about implementing
ahash support similar to dm-verity this version now adds support
for ahash but does not replace the shash support. For more details
see the text of the patch header.
Harald Freudenberger (2):
dm-integrity: use internal variable for digestsize
dm-integrity: introduce ahash support for the internal hash
drivers/md/dm-integrity.c | 237 +++++++++++++++++++++++++++++---------
1 file changed, 180 insertions(+), 57 deletions(-)
base-commit: fac04efc5c793dccbd07e2d59af9f90b7fc0dca4
--
2.43.0
next reply other threads:[~2025-01-29 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 16:25 Harald Freudenberger [this message]
2025-01-29 16:25 ` [PATCH v2 1/2] dm-integrity: use internal variable for digestsize Harald Freudenberger
2025-01-29 16:25 ` [PATCH v2 2/2] dm-integrity: introduce ahash support for the internal hash Harald Freudenberger
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=20250129162528.57124-1-freude@linux.ibm.com \
--to=freude@linux.ibm.com \
--cc=agk@redhat.com \
--cc=dengler@linux.ibm.com \
--cc=dm-devel@lists.linux.dev \
--cc=herbert@gondor.apana.org.au \
--cc=ifranzki@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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