Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2021550

Summary: poly1305 cipher not working with emulation on aarch64
Product: Red Hat Enterprise Linux 8 Reporter: Honza Horak <hhorak>
Component: opensslAssignee: Sahana Prasad <sahana>
Status: CLOSED CURRENTRELEASE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: low Docs Contact:
Priority: low    
Version: 8.4CC: dbelyavs, zsvetlik
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-24 15:41:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Honza Horak 2021-11-09 15:23:01 UTC
Description of problem:

Originally reported as BZ#2018327: ubi8/nodejs-12 container crashes on non M1 Apple M1 laptop or when running with emulation. While this is not a standard environment, UBI containers are expected to be used on non-RHEL environments, so it's still relevant for RHEL.

The problem is with poly1305 cipher, it's already fixed in upstream:
https://github.com/openssl/openssl/commit/fcf6e9d056162d5af64c6f7209388a5c3be2ce57 (verified it fixes our issue by a scratch build https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=41120457)

We've started to see this after the default cipher set started to be used (BZ#1952915).

Version-Release number of selected component (if applicable):
openssl-1.1.1g-15.el8_3.aarch64

How reproducible:
steadily

Steps to Reproduce:
1. podman run --arch arm64 -ti --rm ubi8/nodejs-12 npm install npm@latest

Actual results:
qemu: uncaught target signal 11 (Segmentation fault) - core dumped11867eb79ea096

Expected results:
no crash

Additional info:
Similar error is seen on Apple M1 laptop that starts to be pretty popular across developers. On that laptop, docker runs on a thin VM that is not patched (upstream kernel already has a fix that might help, but hard to test: https://github.com/torvalds/linux/commit/519a0d7e495a6d3ce62594e485aea2a3a4a2ca0a)

We consider a work-around of removing the problematic cipher from the default list for nodejs only -- do it only in the container and only on aarch64, because that seems to be the only environment that seems to be affected: https://bugzilla.redhat.com/show_bug.cgi?id=2018327#c23

However, we would appreciate this being fixed in RHEL-8 openssl to have a proper fix and enable the problematic cipher to be used.

Comment 1 Honza Horak 2021-11-09 15:26:55 UTC
It's more a wild guess, but https://bugzilla.redhat.com/show_bug.cgi?id=2006351 might be related.

Comment 2 Honza Horak 2021-11-10 18:51:52 UTC
With RHEL-8.5, we don't see any issue any more. This is likely a consequence of the rebase, that touched the problematic cipher as well:

--- openssl-1.1.1g/crypto/poly1305/asm/poly1305-armv8.pl	2021-11-10 19:45:13.752782656 +0100
+++ openssl-1.1.1k/crypto/poly1305/asm/poly1305-armv8.pl	2021-11-10 19:44:36.607639666 +0100
@@ -58,10 +58,14 @@ $code.=<<___;
 
 // forward "declarations" are required for Apple
 .extern	OPENSSL_armcap_P
+.hidden	OPENSSL_armcap_P
+.globl	poly1305_init
+.hidden	poly1305_init
 .globl	poly1305_blocks
+.hidden	poly1305_blocks
 .globl	poly1305_emit
+.hidden	poly1305_emit
 
-.globl	poly1305_init
 .type	poly1305_init,%function
 .align	5
 poly1305_init:
@@ -861,8 +865,8 @@ poly1305_blocks_neon:
 	st1	{$ACC4}[0],[$ctx]
 
 .Lno_data_neon:
-	.inst	0xd50323bf		// autiasp
 	ldr	x29,[sp],#80
+	.inst	0xd50323bf		// autiasp
 	ret
 .size	poly1305_blocks_neon,.-poly1305_blocks_neon


Feel free to close if you don't see any other reason to track this issue any more either.

Comment 3 Dmitry Belyavskiy 2022-02-24 15:41:06 UTC
Honza, thanks, closing it