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.

Description of problem:

When stracing systemd (PID 1), I can see the following message:

# strace -fttTvyy -o systemd.strace -s 1024 -p 1
strace: Process 1 attached
...
strace: xlat_idx: Unexpected xlat value 0 at index 4


Version-Release number of selected component (if applicable):

strace-4.24-2.el8.x86_64


How reproducible:

Always


Steps to Reproduce:
1. strace systemd

  # strace -fttTvyy -o systemd.strace -s 1024 -p 1

2. restart systemd-logind

  # systemctl restart systemd-logind.service

Actual results:

strace: Process 1 attached
strace: Process 1901 attached
strace: xlat_idx: Unexpected xlat value 0 at index 4

Expected results:

strace: Process 1 attached
strace: Process 1901 attached

Fixed in upstream:
https://gitlab.com/strace/strace/commit/8a5feb1cb331441d1b721b6455ee95b50258dbac "evdev: fix off-by-one error in decode_bitset"

Related commits:
https://gitlab.com/strace/strace/commit/b2c63fa8973442747de715ff5ff5340383e7b69d "nlattr: fix off-by-one error in indexed xlat lookup"
https://gitlab.com/strace/strace/commit/986a55423eb8e16a7cd0b249ce8e18465f0650f4 "aio: fix off-by-one error in indexed xlat lookup"
https://gitlab.com/strace/strace/commit/d0ae0b3dcabfd61dd2134422114570862fdca283 "rtnl_link: fix off-by-one errors in indexed and sorted xlat lookups"
https://gitlab.com/strace/strace/commit/b967e34d70895b799d16f5d45a9a5228d7eb73a3 "xlat_idx: do not issue warnings for holes in indices"
https://gitlab.com/strace/strace/commit/99300f217b7870fcaa752e1350a33cf98d61a993 "evdev: fix decoding of bit sets"
https://gitlab.com/strace/strace/commit/5ee385e2eb9288ae49e07dca67e576abb2e10fea "evdev: fix decoding of EVIOCGBIT(0, ...)"

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, 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-2019:3642