Re: [PATCH] nfsd: Don't force CRYPTO_LIB_SHA256 to be built-in

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

 



On 9/3/25 10:29 PM, Eric Biggers wrote:
> On Sun, Aug 03, 2025 at 02:21:30PM -0700, Eric Biggers wrote:
>> Now that nfsd is accessing SHA-256 via the library API instead of via
>> crypto_shash, there is a direct symbol dependency on the SHA-256 code
>> and there is no benefit to be gained from forcing it to be built-in.
>> Therefore, select CRYPTO_LIB_SHA256 from NFSD (conditional on NFSD_V4)
>> instead of from NFSD_V4, so that it can be 'm' if NFSD is 'm'.
>>
>> Signed-off-by: Eric Biggers <ebiggers@xxxxxxxxxx>
>> ---
>>  fs/nfsd/Kconfig | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Looks like this patch hasn't been applied yet.  Could it be taken
> through the nfs tree?  Thanks,
> 
> - Eric

For some reason, I marked this patch "superceded" in patchworks so it
got lost. I can apply it today.


-- 
Chuck Lever




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux