From: Steve Grubb <sgrubb@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Richard Guy Briggs <rgb@redhat.com>, linux-audit@redhat.com
Subject: Re: [PATCH v2] audit: add feature audit_lost reset
Date: Thu, 15 Dec 2016 22:12:00 -0500 [thread overview]
Message-ID: <14416625.8shW6piCVY@x2> (raw)
In-Reply-To: <CAHC9VhS4yCw6bfYJVLOzy1VOZnF+FZyA8wS3O6UjVT4SZ45KUA@mail.gmail.com>
On Thursday, December 15, 2016 7:50:48 PM EST Paul Moore wrote:
> On Thu, Dec 15, 2016 at 7:22 PM, Steve Grubb <sgrubb@redhat.com> wrote:
> > I'm planning to replace all the config change logging with the
> > audit_log_task_simple function I sent so that we have everything. Can we
> > go ahead and pull that in so that we can start using it?
>
> There needs to be more than one user of the function to make it
> worthwhile; so far that function has only been proposed with a single
> user. Propose it with multiple users and we can look at it seriously.
That's because I have several unrelated patches that use it. Do you want me to
send all of them at once? There's going to be at least 5 users of the
function. Possibly more. I want it to be the default for all future events
added because it concisely gives the necessary information for well-formed
events.
-Steve
next prev parent reply other threads:[~2016-12-16 3:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 11:52 [PATCH v2] audit: add feature audit_lost reset Richard Guy Briggs
2016-12-15 20:39 ` Paul Moore
2016-12-16 0:22 ` Steve Grubb
2016-12-16 0:50 ` Paul Moore
2016-12-16 3:12 ` Steve Grubb [this message]
2016-12-16 3:39 ` Richard Guy Briggs
2016-12-16 22:47 ` Paul Moore
2016-12-16 3:59 ` Richard Guy Briggs
2016-12-16 3:54 ` 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=14416625.8shW6piCVY@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=paul@paul-moore.com \
--cc=rgb@redhat.com \
/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