public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Harald Freudenberger <freude@linux.ibm.com>
To: agk@redhat.com, snitzer@kernel.org, mpatocka@redhat.com,
	ifranzki@linux.ibm.com
Cc: linux-s390@vger.kernel.org, dm-devel@lists.linux.dev,
	herbert@gondor.apana.org.au, dengler@linux.ibm.com
Subject: [PATCH v1 0/1] dm-integrity: Implement asynch digest support
Date: Wed, 15 Jan 2025 17:46:56 +0100	[thread overview]
Message-ID: <20250115164657.84650-1-freude@linux.ibm.com> (raw)

Use the async digest in-kernel crypto API instead of the
synchronous digest API. This has the advantage of being able
to use synchronous as well as asynchronous digest implementations
as the in-kernel API has an automatic wrapping mechanism
to provide all synchronous digests via the asynch API.

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.

Harald Freudenberger (1):
  dm-integrity: Implement asynch digest support

 drivers/md/dm-integrity.c | 220 ++++++++++++++++++++++++--------------
 1 file changed, 138 insertions(+), 82 deletions(-)


base-commit: fac04efc5c793dccbd07e2d59af9f90b7fc0dca4
--
2.43.0


             reply	other threads:[~2025-01-15 16:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15 16:46 Harald Freudenberger [this message]
2025-01-15 16:46 ` [PATCH v1 1/1] dm-integrity: Implement asynch digest support Harald Freudenberger
2025-01-15 17:29   ` Mikulas Patocka
2025-01-17 13:31     ` Harald Freudenberger
2025-01-22 17:00     ` Harald Freudenberger
2025-01-27 17:57       ` Mikulas Patocka
2025-01-15 17:37   ` Eric Biggers
2025-01-16  7:33     ` Harald Freudenberger
2025-01-16  8:03       ` Eric Biggers
2025-01-16  9:00         ` Harald Freudenberger
2025-01-16  9:12           ` Herbert Xu
2025-01-16 17:54             ` Eric Biggers
2025-01-17  6:21               ` Herbert Xu
2025-01-17  7:57                 ` Eric Biggers

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=20250115164657.84650-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