Bug 2203636 - Unhandled amd64-linux syscall 441 (epoll_pwait2) error reported
Summary: Unhandled amd64-linux syscall 441 (epoll_pwait2) error reported
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: valgrind
Version: 38
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Mark Wielaard
QA Contact: Fedora Extras Quality Assurance
URL: https://performancecopilot.github.io/...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-14 22:32 UTC by Nathan Scott
Modified: 2023-05-28 02:56 UTC (History)
6 users (show)

Fixed In Version: valgrind-3.21.0-4.fc38 valgrind-3.21.0-4.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-20 01:48:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 460192 0 NOR UNCONFIRMED Add epoll_pwait2 2023-05-14 22:45:48 UTC

Description Nathan Scott 2023-05-14 22:32:27 UTC
We're seeing quite a few cases of this warning during PCP CI on f38
and rawhide (for several weeks now, sorry, been a bit slow reporting)
... one case I looked at was in a program using libuv, and a little
poking around in kernel headers suggests this may be a epoll related
syscall, recently added I guess.

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

I don't have an account there in kde land, so opening here for
expediency - thanks Mark!!! :)

Reproducible: Always

Steps to Reproduce:
1. Run PCP CI  :P

Actual Results:  
A warning is reported from valgrind.

Expected Results:  
No warning is reported from valgrind.

Comment 1 Mark Wielaard 2023-05-14 22:45:49 UTC
This is epoll_pwait2 also reported upstream:
https://bugs.kde.org/show_bug.cgi?id=460192
which already has a patch

Comment 2 Nathan Scott 2023-05-14 23:08:51 UTC
Great, thanks Mark - my Google skills have let me down.  :P  Not sure why that didn't come up, but good to know its (near) fixed.

cheers.

Comment 3 Fedora Update System 2023-05-17 13:20:23 UTC
FEDORA-2023-be03eeb1f3 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-be03eeb1f3

Comment 4 Fedora Update System 2023-05-18 02:06:49 UTC
FEDORA-2023-be03eeb1f3 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-be03eeb1f3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-be03eeb1f3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2023-05-19 09:58:57 UTC
FEDORA-2023-51f42b3ae1 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-51f42b3ae1

Comment 6 Fedora Update System 2023-05-20 01:48:00 UTC
FEDORA-2023-be03eeb1f3 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2023-05-20 10:22:12 UTC
FEDORA-2023-51f42b3ae1 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-51f42b3ae1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-51f42b3ae1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2023-05-28 02:56:18 UTC
FEDORA-2023-51f42b3ae1 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.