From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751650AbdF1TI1 (ORCPT ); Wed, 28 Jun 2017 15:08:27 -0400 Received: from mail-lf0-f48.google.com ([209.85.215.48]:34744 "EHLO mail-lf0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751511AbdF1TIV (ORCPT ); Wed, 28 Jun 2017 15:08:21 -0400 MIME-Version: 1.0 X-Originating-IP: [108.49.102.27] In-Reply-To: <20170627204537.GD27193@madcap2.tricolour.ca> References: <20170627204537.GD27193@madcap2.tricolour.ca> From: Paul Moore Date: Wed, 28 Jun 2017 15:08:19 -0400 Message-ID: Subject: Re: [PATCH ALT4 V2 2/2] audit: filter PATH records keyed on filesystem magic To: Richard Guy Briggs Cc: linux-kernel@vger.kernel.org, linux-audit@redhat.com, Greg Kroah-Hartman , Steven Rostedt , Ingo Molnar , Al Viro Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 27, 2017 at 4:45 PM, Richard Guy Briggs wrote: > On 2017-05-30 17:30, Paul Moore wrote: >> On Tue, Apr 4, 2017 at 5:21 AM, Richard Guy Briggs wrote: >> > Tracefs or debugfs were causing hundreds to thousands of PATH records to >> > be associated with the init_module and finit_module SYSCALL records on a >> > few modules when the following rule was in place for startup: >> > -a always,exit -F arch=x86_64 -S init_module -F key=mod-load >> > >> > Provide a method to ignore these large number of PATH records from >> > overwhelming the logs if they are not of interest. Introduce a new >> > filter list "AUDIT_FILTER_PATH", with a new field type AUDIT_FSTYPE, >> > which keys off the filesystem 4-octet hexadecimal magic identifier to >> > filter specific filesystem PATH records. >> > >> > An example rule would look like: >> > -a never,path -F fstype=0x74726163 -F key=ignore_tracefs >> > -a never,path -F fstype=0x64626720 -F key=ignore_debugfs >> >> Trying to look into the future I wonder if we are ever going to need >> to expand the "path" filtering to regular inode lookups, e.g. >> audit_inode()? > > That thought had occurred to me. Do you see any concern with that that > would affect this patch in terms of naming? Well, you want to change this to "fs" now instead of "path", right? I think that removes my concerns. > I could see expanding this filter to include other filter fields though > nothing specific comes to mind now. -- paul moore www.paul-moore.com