On Mon, Nov 4, 2019 at 7:39 PM Chris Mason <c...@fb.com> wrote: > On 4 Nov 2019, at 19:15, Paul Moore wrote: > > > On Fri, Nov 1, 2019 at 9:24 AM Chris Mason <c...@fb.com> wrote: > >> On 31 Oct 2019, at 19:27, Paul Moore wrote: > >>> It's been a while, but I thought we suggested Dave try running > >>> 'auditctl -a never,task' to see if that would solve his problem and > >>> I > >>> believe his answer was no, which confused me a bit as the > >>> audit_filter_task() call in audit_alloc() should see that rule and > >>> return a state of AUDIT_DISABLED which not only prevents > >>> audit_alloc() > >>> from allocating an audit_context (and remember if the audit_context > >>> is > >>> NULL then audit_dummy_context() returns true), but it also clears > >>> the > >>> TIF_SYSCALL_AUDIT flag (which I'm guessing you also want). > >> > >> Thanks for the reminder on this part, I meant to test it. Yes, > >> auditctl > >> -a never,task does stop the messages, even without my patch applied. > > > > I'm glad to hear that worked, I was going to be *very* confused if you > > came back and said you were still seeing NTP records. > > > > I would suggest that regardless of what happens with audit_enabled you > > likely want to keep this audit rule as part of your boot > > configuration, not only does it squelch the audit records, but it > > should improve performance as well (at the cost of no syscall > > auditing). A number of Linux distros have this as their default at > > boot. > > > > Definitely, we'll be testing auditctl -a never,task internally. Before > we went down that path I wanted to fully understand what was going on, > but I think all the big questions have been answered at this point.
Yes, that is why we didn't do anything earlier with Dave's reports; we couldn't reconcile the results with the code, and the lack of other similar problem reports made me suspicious. As you said, we understand things a bit better now. > I'm happy to try variations on my patch, but if you want to include it, > please do remember that I've really only tested it with auditing off. Understood. FWIW, I'm not overly in love with the approach in the patch you posted, but I haven't looked too seriously into alternatives thus far. I expect with most everyone running with the "never" audit rule installed this solves this just fine for the time being. -- paul moore www.paul-moore.com -- Linux-audit mailing list Linux-audit@redhat.com https://www.redhat.com/mailman/listinfo/linux-audit