From: Steven Rostedt <rostedt@goodmis.org>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: Paul Moore <paul@paul-moore.com>,
Linux-Audit Mailing List <linux-audit@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@redhat.com>, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: Hundreds of null PATH records for *init_module syscall audit logs
Date: Tue, 7 Mar 2017 10:41:39 -0500 [thread overview]
Message-ID: <20170307104139.38f5cd38@gandalf.local.home> (raw)
In-Reply-To: <20170307033954.GS18258@madcap2.tricolour.ca>
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.
-- Steve
next prev parent reply other threads:[~2017-03-07 15:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 3:15 Richard Guy Briggs
2017-03-01 3:24 ` [PATCH ALT1] audit: ignore tracefs and debugfs on inode child Richard Guy Briggs
2017-03-01 3:26 ` [PATCH ALT3] audit: hide PATH records of anonymous parents and their children Richard Guy Briggs
2017-03-01 3:29 ` [PATCH ALT2] audit: don't create PATH records for " Richard Guy Briggs
2017-03-01 3:29 ` [PATCH ALT4] audit: show fstype:pathname for entries with anonymous parents Richard Guy Briggs
2017-03-02 12:58 ` kbuild test robot
2017-03-01 3:37 ` Hundreds of null PATH records for *init_module syscall audit logs Richard Guy Briggs
2017-03-01 4:15 ` Steve Grubb
2017-03-03 21:14 ` Richard Guy Briggs
2017-03-03 22:24 ` [PATCH ALT5] audit: ignore module syscalls on inode child Richard Guy Briggs
2017-03-04 0:22 ` Hundreds of null PATH records for *init_module syscall audit logs Paul Moore
2017-03-06 21:49 ` Richard Guy Briggs
2017-03-06 22:30 ` Jessica Yu
2017-03-07 3:46 ` Richard Guy Briggs
2017-03-09 13:25 ` Steve Grubb
2017-03-09 13:24 ` Steve Grubb
2017-03-04 0:19 ` Paul Moore
2017-03-07 3:39 ` Richard Guy Briggs
2017-03-07 15:41 ` Steven Rostedt [this message]
2017-03-07 16:00 ` Richard Guy Briggs
2017-03-07 16:20 ` Steven Rostedt
2017-03-07 17:39 ` Richard Guy Briggs
2017-03-07 18:04 ` Steven Rostedt
2017-03-07 18:34 ` Richard Guy Briggs
2017-03-07 19:09 ` Steven Rostedt
2017-03-07 22:00 ` Richard Guy Briggs
2017-03-09 13:33 ` Steve Grubb
2017-03-07 15:37 ` Steven Rostedt
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=20170307104139.38f5cd38@gandalf.local.home \
--to=rostedt@goodmis.org \
--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=rgb@redhat.com \
--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®