lkml.org 
[lkml]   [2017]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Hundreds of null PATH records for *init_module syscall audit logs
On Tue, 7 Mar 2017 11:00:27 -0500
Richard Guy Briggs <rgb@redhat.com> wrote:

> On 2017-03-07 10:41, Steven Rostedt wrote:
> > On Mon, 6 Mar 2017 22:39:54 -0500
> > Richard Guy Briggs <rgb@redhat.com> wrote:
> >
> > > >From the output I've seen, it doesn't look particularly useful, but it
> > > was useful to finally see the source of those huge numbers of PATH
> > > records. Here's an fpaste:
> > > https://paste.fedoraproject.org/paste/UpZoYuokojR0es1ayNdx5l5M1UNdIGYhyRLivL9gydE=/
> >
> > Those are the files for the module's trace events that are created.
> >
> > I'm still confused about what the issue is.
>
> The issue is the audit subsystem being overwhelmed by potentially
> useless information.
>
> The initial report was "there's a bunch of null PATH records, please
> make them go away", which was anywhere from 500 to 6000 records.

I don't know the audit system and exactly what it is looking for. How
does it deal with other virtual filesystems like procfs? Why is tracefs
different?

-- Steve

\
 
 \ /
  Last update: 2017-03-07 17:22    [W:0.429 / U:0.476 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site