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.
DescriptionJan Pazdziora (Red Hat)
2019-08-13 16:01:13 UTC
Description of problem:
The man page for auditctl(8) says:
--backlog_wait_time wait_time
Set the time for the kernel to wait (Kernel Default 60*HZ) when
the backlog_limit is reached before queuing more audit events to
be transferred to auditd. The number must be greater than or
equal to zero and less that 10 times the default value.
However, nowhere in that page is backlog_limit defined or explained. Is that a CLI option, is that auditd config parameter, is that some kernel thing? It is written with an underscore so I assume it refers to some value that can be queried and set but how to do it?
Version-Release number of selected component (if applicable):
audit-3.0-0.10.20180831git0047a6c.el8.x86_64
How reproducible:
Deterministic.
Steps to Reproduce:
1. Read the man page for auditctl(8) and try to figure out in which situation will the kernel wait that wait_time interval.
Actual results:
No explanation of backlog_limit.
Expected results:
Some explanation of backlog_limit.
Additional info:
Acceptance Criteria:
* backlog limit is explained in man page.
Successfully verified:
OLD (audit-3.0-0.13.20190507gitf58ec40.el8)
===========================================
-b backlog
Set max number of outstanding audit buffers allowed (Kernel Default=64) If all buffers are full, the
failure flag is consulted by the kernel for action.
--backlog_wait_time wait_time
Set the time for the kernel to wait (Kernel Default 60*HZ) when the backlog_limit is reached before
queuing more audit events to be transferred to auditd. The number must be greater than or equal to
zero and less that 10 times the default value.
NEW (audit-3.0-0.15.20191104git1c2f876.el8)
===========================================
-b backlog
Set max number (limit) of outstanding audit buffers allowed (Kernel Default=64) If all buffers are
full, the failure flag is consulted by the kernel for action.
--backlog_wait_time wait_time
Set the time for the kernel to wait (Kernel Default 60*HZ) when the backlog limit is reached before
queuing more audit events to be transferred to auditd. The number must be greater than or equal to
zero and less that 10 times the default value.
Backlog limit is explained [*] in '-b' option description preceding --backlog_wait option description.
[*] max number of outstanding audit buffers allowed
One more nitpick to fix upstream - missing dot after "(Kernel Default=64)' (...allowed (Kernel Default=64) If...).
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-2020:1812
Description of problem: The man page for auditctl(8) says: --backlog_wait_time wait_time Set the time for the kernel to wait (Kernel Default 60*HZ) when the backlog_limit is reached before queuing more audit events to be transferred to auditd. The number must be greater than or equal to zero and less that 10 times the default value. However, nowhere in that page is backlog_limit defined or explained. Is that a CLI option, is that auditd config parameter, is that some kernel thing? It is written with an underscore so I assume it refers to some value that can be queried and set but how to do it? Version-Release number of selected component (if applicable): audit-3.0-0.10.20180831git0047a6c.el8.x86_64 How reproducible: Deterministic. Steps to Reproduce: 1. Read the man page for auditctl(8) and try to figure out in which situation will the kernel wait that wait_time interval. Actual results: No explanation of backlog_limit. Expected results: Some explanation of backlog_limit. Additional info: