From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: Hundreds of null PATH records for *init_module syscall audit logs Date: Tue, 7 Mar 2017 11:20:56 -0500 Message-ID: <20170307112056.4e27424a@gandalf.local.home> References: <20170301031549.GT18258@madcap2.tricolour.ca> <20170301033704.GU18258@madcap2.tricolour.ca> <20170307033954.GS18258@madcap2.tricolour.ca> <20170307104139.38f5cd38@gandalf.local.home> <20170307160027.GB10258@madcap2.tricolour.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170307160027.GB10258@madcap2.tricolour.ca> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Richard Guy Briggs Cc: Kroah-Hartman , LKML , Ingo Molnar , Al Viro , Linux-Audit Mailing List , Greg@redhat.com List-Id: linux-audit@redhat.com On Tue, 7 Mar 2017 11:00:27 -0500 Richard Guy Briggs wrote: > On 2017-03-07 10:41, Steven Rostedt wrote: > > On Mon, 6 Mar 2017 22:39:54 -0500 > > Richard Guy Briggs 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