Bug 2031547

Summary: RFE: Please enable BLAKE2B support in the kernel
Product: Red Hat Enterprise Linux 9 Reporter: Neal Gompa <ngompa13>
Component: kernelAssignee: Vladis Dronov <vdronov>
kernel sub component: Crypto QA Contact: Linqing Lu <lilu>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: bstinson, bugzilla, carl, davide, herbert.xu, jbilling, jpazdziora, jwboyer, michel, peter.georg, rparrazo, ssorce, vdronov, vreeland.justin
Version: CentOS StreamKeywords: FutureFeature
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kernel-5.14.0-42.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 15:43:16 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Neal Gompa 2021-12-12 18:55:03 UTC
Description of problem:
To support downstream work by the CentOS Hyperscale SIG, it would be appreciated if CONFIG_CRYPTO_BLAKE2B=m could be set in the RHEL kernel configuration.

In particular, this would help us with supporting Btrfs downstream in the CentOS Stream 9 Hyperscale variant in our kernel and working with the CentOS Kmods SIG to support it as a third-party kernel module package built by them.

Version-Release number of selected component (if applicable):
5.14.0-29.el9

Comment 3 Neal Gompa 2021-12-12 19:27:59 UTC
MR for CKI for ARK proposed: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1524

Comment 4 Peter Georg 2021-12-14 18:24:47 UTC
Just a short comment to confirm that the Kmods SIG would very much appreciate this change (hence Jonathan and myself added to CC).

Comment 6 Simo Sorce 2021-12-16 01:34:31 UTC
Blake2b would be disabled in FIPS mode so there should be no problem.

Comment 17 errata-xmlrpc 2022-05-17 15:43:16 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: kernel), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:3907