Bug 2030872

Summary: valgrind: Please handle the rseq system call
Product: Red Hat Enterprise Linux 9 Reporter: Florian Weimer <fweimer>
Component: valgrindAssignee: Mark Wielaard <mjw>
valgrind sub component: system-version QA Contact: Jesus Checa <jchecahi>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: aoliva, arjun.is, codonell, dj, extras-qa, fche, fweimer, jakub, law, mcermak, mfabian, ohudlick, pfrankli, rth, sipoyare
Version: 9.0Keywords: Patch, Triaged
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: valgrind-3.18.1-6.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 2030870 Environment:
Last Closed: 2022-05-17 12:48: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:
Bug Depends On: 2030870    
Bug Blocks: 2024347    
Deadline: 2022-01-10   

Description Florian Weimer 2021-12-09 23:02:38 UTC
+++ This bug was initially created as a clone of Bug #2030870 +++

We plan to backport rseq-backed sched_getcpu into Red Hat Enterprise Linux 9 (bug 2024347).

--2062070-- WARNING: unhandled amd64-linux syscall: 334
--2062070-- You may be able to write your own handler.
--2062070-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2062070-- Nevertheless we consider this a bug.  Please report
--2062070-- it at http://valgrind.org/support/bug_reports.html.

Failing the rseq system call with ENOSYS is fine, there is a fallback.

Comment 1 Mark Wielaard 2021-12-10 22:27:55 UTC
Proposed patch upstream: https://bugs.kde.org/show_bug.cgi?id=405377
And test build is in fedora rawhide valgrind-3.18.1-6.fc36

Comment 7 errata-xmlrpc 2022-05-17 12:48:06 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: valgrind), 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:2401