Re: [PATCH v2] fsverity: use shash API instead of ahash API

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Eric Biggers <ebiggers@xxxxxxxxxx>
Subject: Re: [PATCH v2] fsverity: use shash API instead of ahash API
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 19 May 2023 22:10:15 -0700
Cc: fsverity@xxxxxxxxxxxxxxx, linux-crypto@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, linux-f2fs-devel@xxxxxxxxxxxxxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx
In-reply-to: <20230516052306.99600-1-ebiggers@kernel.org>
References: <20230516052306.99600-1-ebiggers@kernel.org>

I'm not really an expert on fsverify, but the rationale of not using
clumsy external crypto offloads from the file system makes sense, and
the code looks much nicer now:

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

References:
- [PATCH v2] fsverity: use shash API instead of ahash API
  - From: Eric Biggers

Prev by Date: Re: [PATCH v21 18/30] ext4: Provide a splice-read stub
Next by Date: Re: [PATCH v21 18/30] ext4: Provide a splice-read stub
Previous by thread: [PATCH v2] fsverity: use shash API instead of ahash API
Next by thread: Re: [PATCH v2] fsverity: use shash API instead of ahash API
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]

Powered by Linux