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:
systemd in debug mode logs messages like,

[    1.625335] systemd[146]: Failed to add rule for system call set_thread_area() / 205, ignoring: Numerical argument out of domain
[    1.625366] systemd[146]: Failed to add rule for system call signal() / -10055, ignoring: Numerical argument out of domain
[    1.625421] systemd[146]: Failed to add rule for system call olduname() / -10038, ignoring: Numerical argument out of domain
[    1.625495] systemd[146]: Failed to add rule for system call lstat64() / -10028, ignoring: Numerical argument out of domain
[    1.625522] systemd[146]: Failed to add rule for system call getresuid32() / -10020, ignoring: Numerical argument out of domain


Version-Release number of selected component (if applicable):
systemd-239-10.el8

How reproducible:
always

Steps to Reproduce:
1. add "debug" to kernel cmdline
2. reboot
3. journalctl -b _PID=1

Actual results:
Messages similar to above present in the log.

Expected results:
No such noise in the log.

Additional info:
https://github.com/systemd/systemd/commit/b54f36c604472ffe08830ec4306fa2885b4a5424

Set exception- per Jan10th blocker/exception meeting; wait for 8.1

The blocker & exception review process declined this bug for an exception in the current release.  Consequently the following action is being taken:

1. The request for exception is being cleared.
2. The Internal Target Release is being cleared.

All Acks have been retained, meaning you can immediately complete the work in a later release without an exception.  To do this take the following actions:

1. Set the Internal Target Release to the version where you will complete the work.
2. Ask Release Engineering to create the branch if it does not already exist.

fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/256 -> post

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/RHSA-2019:3592