mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Guy Briggs <rgb@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-kernel@vger.kernel.org, linux-audit@redhat.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH ALT4 V2 2/2] audit: filter PATH records keyed on filesystem magic
Date: Wed, 28 Jun 2017 17:25:06 -0400	[thread overview]
Message-ID: <20170628212506.GF27193@madcap2.tricolour.ca> (raw)
In-Reply-To: <CAHC9VhSxd+y6zfsW1OJ4JXooYZi0NMvG-hPRU1qX6f-1PjyqVw@mail.gmail.com>

On 2017-06-28 15:08, Paul Moore wrote:
> On Tue, Jun 27, 2017 at 4:45 PM, Richard Guy Briggs <rgb@redhat.com> wrote:
> > On 2017-05-30 17:30, Paul Moore wrote:
> >> On Tue, Apr 4, 2017 at 5:21 AM, Richard Guy Briggs <rgb@redhat.com> 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.

That's fixed in my cleanup that I'm waiting to push.  In fact it is
"filesystem" in the userspace patch.

> > I could see expanding this filter to include other filter fields though
> > nothing specific comes to mind now.
> 
> paul moore

- RGB

--
Richard Guy Briggs <rgb@redhat.com>
Sr. S/W Engineer, Kernel Security, Base Operating Systems
Remote, Ottawa, Red Hat Canada
IRC: rgb, SunRaycer
Voice: +1.647.777.2635, Internal: (81) 32635

  reply	other threads:[~2017-06-28 21:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04  9:21 [PATCH ALT4 V2 1/2] audit: show fstype:pathname for entries with anonymous parents Richard Guy Briggs
2017-04-04  9:21 ` [PATCH ALT4 V2 2/2] audit: filter PATH records keyed on filesystem magic Richard Guy Briggs
2017-04-04 10:02   ` Richard Guy Briggs
2017-05-30 21:30   ` Paul Moore
2017-06-27 20:45     ` Richard Guy Briggs
2017-06-28 19:08       ` Paul Moore
2017-06-28 21:25         ` Richard Guy Briggs [this message]
2017-04-04 21:19 ` [PATCH ALT4 V2 1/2] audit: show fstype:pathname for entries with anonymous parents Paul Moore
2017-04-05  4:18   ` Richard Guy Briggs
2017-05-30 21:21 ` Paul Moore
2017-06-27 21:11   ` Richard Guy Briggs
2017-06-28 19:03     ` Paul Moore
2017-06-29 21:21       ` Richard Guy Briggs
2017-06-29 23:58         ` Steven Rostedt
2017-06-30 13:07           ` Richard Guy Briggs
2017-08-11  6:36       ` Richard Guy Briggs
2017-08-14  4:32         ` Richard Guy Briggs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170628212506.GF27193@madcap2.tricolour.ca \
    --to=rgb@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=rostedt@goodmis.org \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®