Red Hat Bugzilla – Bug 434158
[AUDIT] printk ratelimiting can cause a regression (panic)
Last modified: 2008-05-21 11:10:34 EDT
Introduced rate limiting into the audit code for its use of printk. This code
makes it very easy to panic the box assuming the user chose to panic on audit
failure. The most likely scenario? Load more than about 12 rules and try to
reboot. auditd shuts down before the rules are unloaded so the audit system
switches to using printk. We emit a message for every rule loaded so we emit
more than 10 messages (the printk ratelimit default burst) thus we lose a
message. If the user selected to panic on lost message the box will panic!
I submitted an RFC upstream:
and hopefully noone will object....
Patch was accepted into mainline kernel as: commit
You can download this test kernel from http://people.redhat.com/dzickus/el5
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.