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 1984076 - glibc 2.34 usage of clone3 breaks thread using programs under valgrind
Summary: glibc 2.34 usage of clone3 breaks thread using programs under valgrind
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: valgrind
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Mark Wielaard
QA Contact: Jesus Checa
URL:
Whiteboard:
Depends On: 1984075
Blocks: 1983628 1984831
TreeView+ depends on / blocked
 
Reported: 2021-07-20 15:20 UTC by Florian Weimer
Modified: 2021-12-07 21:34 UTC (History)
9 users (show)

Fixed In Version: valgrind-3.17.0-9.el9
Doc Type: No Doc Update
Doc Text:
Clone Of: 1984075
Environment:
Last Closed: 2021-12-07 21:33:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 420906 0 NOR ASSIGNED missing syscall wrapper for clone3 (435) 2021-07-21 12:26:43 UTC

Description Florian Weimer 2021-07-20 15:20:27 UTC 
+++ This bug was initially created as a clone of Bug #1984075 +++

glibc 2.34 tries to use the clone3 system call to create threads.

This change is already included in builds glibc-2.33.9000-44.fc35 and later (only in Koji, not tagged into the buildroot/compose).

Currently, valgrind prints a warning for every clone3 system call, which can be reproduced e.g. with Python:

$ valgrind python3
==3260== Memcheck, a memory error detector
==3260== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==3260== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info
==3260== Command: python3
==3260== 
Python 3.10.0b4 (default, Jul 16 2021, 00:00:00) [GCC 11.1.1 20210623 (Red Hat 11.1.1-6)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import threading
>>> threading.Thread(None, lambda: print("Thread is running")).start()
--3260-- WARNING: unhandled amd64-linux syscall: 435
--3260-- You may be able to write your own handler.
--3260-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--3260-- Nevertheless we consider this a bug.  Please report
--3260-- it at http://valgrind.org/support/bug_reports.html.
Thread is running
>>> 

The thread is still launched, but the warning is annoying.
Comment 1 Mark Wielaard 2021-07-21 12:26:47 UTC 
Upstream bugzilla contains a workaround making clone3 produce ENOSYS so glibc falls back on clone.
Currently being tested in Fedora rawhide.
Comment 5 Jesus Checa 2021-08-09 08:33:05 UTC 
Preverified that the bug is fixed in the latest build valgrind-3.17.0-10.el9 and glibc-2.33.9000-55.el9.

With valgrind-3.17.0-8.el9:
[root@sweetpig-8 ~]# valgrind python3 -c "import threading; threading.Thread(None, lambda:print('Thread is running')).start()"                                                                                                                 
==20786== Memcheck, a memory error detector
==20786== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==20786== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info
==20786== Command: python3 -c import\ threading;\ threading.Thread(None,\ lambda:print('Thread\ is\ running')).start()
==20786== 
--20786-- WARNING: unhandled amd64-linux syscall: 435
--20786-- You may be able to write your own handler.
--20786-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20786-- Nevertheless we consider this a bug.  Please report
--20786-- it at http://valgrind.org/support/bug_reports.html.
Thread is running
==20786== 
==20786== HEAP SUMMARY:
==20786==     in use at exit: 839,345 bytes in 8,158 blocks
==20786==   total heap usage: 38,978 allocs, 30,820 frees, 5,531,067 bytes allocated
==20786== 
==20786== LEAK SUMMARY:
==20786==    definitely lost: 0 bytes in 0 blocks
==20786==    indirectly lost: 0 bytes in 0 blocks
==20786==      possibly lost: 830,780 bytes in 8,101 blocks
==20786==    still reachable: 8,565 bytes in 57 blocks
==20786==         suppressed: 0 bytes in 0 blocks
==20786== Rerun with --leak-check=full to see details of leaked memory
==20786== 
==20786== For lists of detected and suppressed errors, rerun with: -s
==20786== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

With valgrind-3.17.0-10.el9:
valgrind python3 -c "import threading; threading.Thread(None, lambda:print('Thread is running')).start()"
==20972== Memcheck, a memory error detector
==20972== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==20972== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info
==20972== Command: python3 -c import\ threading;\ threading.Thread(None,\ lambda:print('Thread\ is\ running')).start()
==20972== 
Thread is running
==20972== 
==20972== HEAP SUMMARY:
==20972==     in use at exit: 839,345 bytes in 8,158 blocks
==20972==   total heap usage: 38,972 allocs, 30,814 frees, 5,530,747 bytes allocated
==20972== 
==20972== LEAK SUMMARY:
==20972==    definitely lost: 0 bytes in 0 blocks
==20972==    indirectly lost: 0 bytes in 0 blocks
==20972==      possibly lost: 830,780 bytes in 8,101 blocks
==20972==    still reachable: 8,565 bytes in 57 blocks
==20972==         suppressed: 0 bytes in 0 blocks
==20972== Rerun with --leak-check=full to see details of leaked memory
==20972== 
==20972== For lists of detected and suppressed errors, rerun with: -s
==20972== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Also a minor note: this bug affects only x86_64. The rest of archs keep using clone() syscall after glibc2.34 update.
Comment 6 Jesus Checa 2021-08-16 14:24:11 UTC 
Regression testing on valgrind-3.17.0-11.el9 looks good.
Note You need to log in before you can comment on or make changes to this bug.