From: Richard Guy Briggs <rgb@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] audit: use audit_log_task_info in audit_core_dumps and __audit_seccomp
Date: Tue, 14 Jan 2014 14:07:26 -0500 [thread overview]
Message-ID: <20140114190726.GE23577@madcap2.tricolour.ca> (raw)
In-Reply-To: <1840642.Kpxqik9TDB@x2>
On 14/01/14, Steve Grubb wrote:
> On Monday, January 13, 2014 09:56:35 PM Eric Paris wrote:
> > It seems that reusing the task info pattern throughout records should
> > allow for faster simpler more streamlined userspace records parsing, but
> > changing order like this might be a deal breaker.
>
> Have you tried using the ausearch test suite? I published it so that it can be
> found out what all these patches will do to the stability of user space. I'd
> delete your logs, reboot into test kernel, generate as many kind of events as
> possible, then extract the logs and test with the test suite.
Do you have a script of rules and a script of commands to accomplish the
"generate as many kind of events as possible"?
> -Steve
- RGB
--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545
next prev parent reply other threads:[~2014-01-14 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 2:56 [PATCH] audit: use audit_log_task_info in audit_core_dumps and __audit_seccomp Eric Paris
2014-01-14 14:48 ` Steve Grubb
2014-01-14 19:07 ` Richard Guy Briggs [this message]
2014-01-14 19:09 ` Steve Grubb
2014-01-14 18:39 ` Kees Cook
2014-01-15 17:20 ` 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=20140114190726.GE23577@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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