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 1853011

Summary: io_uring_setup.gen.test from strace internal testsuite fails on rhel-8.3
Product: Red Hat Enterprise Linux 8 Reporter: Edjunior Barbosa Machado <emachado>
Component: straceAssignee: Eugene Syromiatnikov <esyr>
strace sub component: system-version QA Contact: Edjunior Barbosa Machado <emachado>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: emachado, ohudlick, skozina
Version: 8.3Flags: pm-rhel: mirror+
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: strace-5.1-2.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 13:28:15 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: 1852960    
Bug Blocks: 1884555, 1894575    

Description Edjunior Barbosa Machado 2020-07-01 17:59:12 UTC
Description of problem:
io_uring_setup.gen.test from strace internal testsuite fails on RHEL-8.3.0-20200701.n.0.

The testcase failure is reproducible on x86_64 (tests and tests-m32), ppc64le and aarch64.


Version-Release number of selected component (if applicable):
strace-5.1-1.el8.src.rpm
gcc-8.3.1-5.1.el8
RHEL-8.3.0-20200701.n.0

How reproducible:
100%

Steps to Reproduce:
1. yum-builddep strace-5.1-1.el8.src.rpm
2. rpm -ivh strace-5.1-1.el8.src.rpm
3. rpmbuild -bc rpmbuild/SPECS/strace.spec
4. make -j2 -k check VERBOSE=1 STRACE=/usr/bin/strace TIMEOUT_DURATION=1500

Actual results:
FAIL: io_uring_setup.gen
========================

+ /usr/bin/strace -V
+ TIMEOUT='timeout -k 5 -s XCPU 1500'
+ timeout -k 5 -s XCPU 1500 true
+ '[' 1 -eq 0 ']'
+ exec timeout -k 5 -s XCPU 1500 ./io_uring_setup.gen.test
+ run_strace_match_diff -a26 -y
+ args='-a26 -y'
+ '[' -n '-a26 -y' -a -z '-a26 -y' ']'
+ set -- -e trace=io_uring_setup -a26 -y
+ run_prog
+ '[' 0 -eq 0 ']'
+ set -- ../io_uring_setup
+ args=../io_uring_setup
+ ../io_uring_setup
+ run_strace -e trace=io_uring_setup -a26 -y ../io_uring_setup
+ args='-e trace=io_uring_setup -a26 -y ../io_uring_setup'
+ /usr/bin/strace -o log -e trace=io_uring_setup -a26 -y ../io_uring_setup
/usr/bin/strace: umoven: short read (119 < 120) @0xf7f75f89
+ match_diff log exp
+ local output expected error
+ '[' 2 -eq 0 ']'
+ output=log
+ shift
+ '[' 1 -eq 0 ']'
+ expected=exp
+ shift
+ '[' 0 -eq 0 ']'
+ error='/usr/bin/strace -e trace=io_uring_setup -a26 -y ../io_uring_setup output mismatch'
+ check_prog diff
+ type diff
+ diff -u -- exp log
--- exp	2020-07-01 13:31:32.073202351 +0200
+++ log	2020-07-01 13:31:32.073202351 +0200
@@ -1,5 +1,5 @@
 io_uring_setup(4294967295, NULL) = -1 EFAULT (Bad address)
 io_uring_setup(0, 0xf7f75f89) = -1 EFAULT (Bad address)
-io_uring_setup(1, {flags=IORING_SETUP_IOPOLL|IORING_SETUP_SQPOLL|IORING_SETUP_SQ_AFF|0xfffffff8, sq_thread_cpu=0x8f8e8d8c, sq_thread_idle=2475856272, resv={0x9f9e9d9c, 0xa3a2a1a0, 0xa7a6a5a4}}) = -1 EINVAL (Invalid argument)
+io_uring_setup(1, {flags=IORING_SETUP_IOPOLL|IORING_SETUP_SQPOLL|IORING_SETUP_SQ_AFF|0xfffffff8, sq_thread_cpu=0x8f8e8d8c, sq_thread_idle=2475856272, resv={0x97969594, 0x9b9a9998, 0x9f9e9d9c, 0xa3a2a1a0, 0xa7a6a5a4}}) = -1 EINVAL (Invalid argument)
 io_uring_setup(2, {flags=0, sq_thread_cpu=0, sq_thread_idle=0, sq_entries=2, cq_entries=4, sq_off={head=0, tail=64, ring_mask=256, ring_entries=264, flags=276, dropped=272, array=392}, cq_off={head=128, tail=192, ring_mask=260, ring_entries=268, overflow=280, cqes=320}}) = 3<anon_inode:[io_uring]>
 +++ exited with 0 +++
+ fail_ '/usr/bin/strace -e trace=io_uring_setup -a26 -y ../io_uring_setup output mismatch'
+ warn_ 'io_uring_setup.gen.test: failed test: /usr/bin/strace -e trace=io_uring_setup -a26 -y ../io_uring_setup output mismatch'
+ printf '%s\n' 'io_uring_setup.gen.test: failed test: /usr/bin/strace -e trace=io_uring_setup -a26 -y ../io_uring_setup output mismatch'
io_uring_setup.gen.test: failed test: /usr/bin/strace -e trace=io_uring_setup -a26 -y ../io_uring_setup output mismatch
+ exit 1
FAIL io_uring_setup.gen.test (exit status: 1)

Comment 11 errata-xmlrpc 2021-05-18 13:28:15 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 (strace bug fix and enhancement update), 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/RHEA-2021:1573