linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Freudenberger <freude@linux.ibm.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dengler@linux.ibm.com, ifranzki@linux.ibm.com, agk@redhat.com,
	snitzer@kernel.org, linux-s390@vger.kernel.org,
	dm-devel@lists.linux.dev, herbert@gondor.apana.org.au,
	Milan Broz <gmazyland@gmail.com>
Subject: Re: [PATCH v4 2/2] dm-integrity: introduce ahash support for the internal hash
Date: Thu, 17 Jul 2025 17:18:00 +0200	[thread overview]
Message-ID: <7c019761106ce58f2e833c38d2a77063@linux.ibm.com> (raw)
In-Reply-To: <50a28342-9d3c-b4e4-de13-40304eabb8b1@redhat.com>

Hi Mikulas

I just want to inform you that I picked up my phmac / dm-integrity work
again after the phmac implementation is about to be merged into the next
mainline kernel 6.17 :-) It has been a long long time to get the phmac
integrated with all the pre-requirements...

There where some issues with running a kernel with your ahash patch
causing a wired kernel crash. However, I'll set up my development
environment now and then let's see if these crashes still occur and
maybe investigate and fix them.

On 2025-02-05 21:23, Mikulas Patocka wrote:
> Introduce ahash support for the "internal hash" algorithm.
> 
> Rework the dm-integrity code to be able to run the "internal hash"
> either with a synchronous ("shash") or asynchronous ("ahash") hash
> algorithm implementation.
> 
...

      parent reply	other threads:[~2025-07-17 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 20:23 [PATCH v4 2/2] dm-integrity: introduce ahash support for the internal hash Mikulas Patocka
2025-02-05 21:24 ` Eric Biggers
2025-02-06 15:22 ` Harald Freudenberger
2025-02-14  9:43 ` Harald Freudenberger
2025-07-17 15:18 ` Harald Freudenberger [this message]

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=7c019761106ce58f2e833c38d2a77063@linux.ibm.com \
    --to=freude@linux.ibm.com \
    --cc=agk@redhat.com \
    --cc=dengler@linux.ibm.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=gmazyland@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).