On Mon, Jul 28, 2025 at 11:24:25PM +0200, Mikulas Patocka wrote:
>
> I'd like to ask the maintainers of crypto-api - Herbert or David - what if
> I pass vmalloc-allocated memory (or possibly stack memory) as "result" to
> ahash_request_set_crypt(req, sg, result, nbytes);? Is it legal or not?
It'
On Mon, 28 Jul 2025, Harald Freudenberger wrote:
> > > > > Mikulas Patocka (2):
> > > > > dm-integrity: use internal variable for digestsize
> > > > > dm-integrity: introduce ahash support for the internal hash
> > > > >
> > > > > drivers/md/dm-integrity.c | 370
> > > > > +
On 2025-07-25 19:38, Eric Biggers wrote:
On Fri, Jul 25, 2025 at 10:14:30AM +0200, Harald Freudenberger wrote:
On 2025-07-24 16:40, Mikulas Patocka wrote:
> On Tue, 22 Jul 2025, Harald Freudenberger wrote:
>
> > Support for ahashes in dm-integrity.
> >
> > Changelog:
> >
> > v1: First implementa
On Fri, Jul 25, 2025 at 10:14:30AM +0200, Harald Freudenberger wrote:
> On 2025-07-24 16:40, Mikulas Patocka wrote:
> > On Tue, 22 Jul 2025, Harald Freudenberger wrote:
> >
> > > Support for ahashes in dm-integrity.
> > >
> > > Changelog:
> > >
> > > v1: First implementation. Tested with crc32,
On 2025-07-24 16:40, Mikulas Patocka wrote:
On Tue, 22 Jul 2025, Harald Freudenberger wrote:
Support for ahashes in dm-integrity.
Changelog:
v1: First implementation. Tested with crc32, sha256, hmac-sha256 and
the s390 specific implementations for hmac-sha256 and protected
key phmac-s
On Tue, 22 Jul 2025, Harald Freudenberger wrote:
> Support for ahashes in dm-integrity.
>
> 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 inst
Support for ahashes in dm-integrity.
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
