+++ This bug was initially created as a clone of Bug #2002756 +++ Description of problem: Version-Release number of selected component (if applicable): glibc-gconv-extra-2.34-2.el9.x86_64 glibc-langpack-en-2.34-2.el9.x86_64 glibc-common-2.34-2.el9.x86_64 glibc-2.34-2.el9.x86_64 How reproducible: * always Steps to Reproduce: # dmesg -c >& /dev/null # find /usr -name vdso64.so /usr/lib/modules/5.14.0-2.el9.x86_64/vdso/vdso64.so # ldd `find /usr -name vdso64.so` ldd: exited with unknown exit code (139) # dmesg [ 506.037367] ld-linux-x86-64[3977]: segfault at 7f36a5450408 ip 00007f36a5459ef5 sp 00007fff73048ba0 error 7 in ld-linux-x86-64.so.2[7f36a5452000+26000] [ 506.037397] Code: 06 00 00 4c 89 e6 48 29 c6 48 83 fe 0a 77 9b be 41 ff ff 6f 48 29 c6 48 89 f0 eb 8a 48 85 ff 74 71 49 8b 47 60 48 85 c0 74 04 <48> 01 78 08 49 8b 47 58 48 85 c0 74 04 48 01 78 08 49 8b 47 68 48 # Actual results: * segfault Expected results: * no segfault
# coredumpctl info -1 PID: 3977 (ld-linux-x86-64) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Thu 2021-09-23 15:14:14 EDT (10min ago) Command Line: /lib64/ld-linux-x86-64.so.2 --verify /usr/lib/modules/5.14.0-2.el9.x86_64/vdso/vdso64.so Executable: /usr/lib64/ld-linux-x86-64.so.2 Control Group: /user.slice/user-0.slice/session-4.scope Unit: session-4.scope Slice: user-0.slice Session: 4 Owner UID: 0 (root) Boot ID: 109b59d7333449f297dc1ceb0ff27a64 Machine ID: 47b7f8cb1ab746f68d985345b84ae331 Hostname: rhel9-machine Storage: /var/lib/systemd/coredump/core.ld-linux-x86-64.0.109b59d7333449f297dc1ceb0ff27a64.3977.1632424454000000.zst (present) Disk Size: 8.2K Message: Process 3977 (ld-linux-x86-64) of user 0 dumped core. Found module /usr/lib/modules/5.14.0-2.el9.x86_64/vdso/vdso64.so with build-id: d39f1a64b35f2ae1462c4d8636636adbb85232df Found module /usr/lib64/ld-linux-x86-64.so.2 with build-id: 018c91b9b8bd54c4b11cdf2a9da09256d4047a76 Found module linux-vdso.so.1 with build-id: d39f1a64b35f2ae1462c4d8636636adbb85232df Stack trace of thread 3977: #0 0x00007f36a5459ef5 elf_get_dynamic_info (/usr/lib64/ld-linux-x86-64.so.2 + 0x8ef5) #1 0x00007f36a545ad38 _dl_map_object (/usr/lib64/ld-linux-x86-64.so.2 + 0x9d38) #2 0x00007f36a54522a9 map_doit (/usr/lib64/ld-linux-x86-64.so.2 + 0x12a9) #3 0x00007f36a546f4ee _dl_catch_exception (/usr/lib64/ld-linux-x86-64.so.2 + 0x1e4ee) #4 0x00007f36a546f593 _dl_catch_error (/usr/lib64/ld-linux-x86-64.so.2 + 0x1e593) #5 0x00007f36a545701f dl_main (/usr/lib64/ld-linux-x86-64.so.2 + 0x601f) #6 0x00007f36a546e497 _dl_sysdep_start (/usr/lib64/ld-linux-x86-64.so.2 + 0x1d497) #7 0x00007f36a545309f _dl_start_final (/usr/lib64/ld-linux-x86-64.so.2 + 0x209f) #8 0x00007f36a5452098 _start (/usr/lib64/ld-linux-x86-64.so.2 + 0x1098) #
We will very likely inherit the upstream fix (once the regressions are addressed) with an upcoming sync with the release/2.34/master stable branch.
Verified on (x86_64, s390x): RHEL-9.0.0-20211115.6 glibc-2.34-8.el9 https://beaker.engineering.redhat.com/tasks/executed?recipe_task_id=135046413&recipe_task_id=135046871&new_pkg_tasks=135046413,135046871
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: glibc), 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:3917