All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: linux-audit@redhat.com
Subject: [RFC PATCH] audit-testsuite: improve our chances of losing records in lost_reset
Date: Thu, 13 Dec 2018 18:17:01 -0500	[thread overview]
Message-ID: <154474302167.32049.14827507134973529836.stgit@chester> (raw)

From: Paul Moore <paul@paul-moore.com>

If the point of the lost_reset test is to flood the system with audit
records, why are we restricting ourselves with a filter?  Let's log
everything.

Signed-off-by: Paul Moore <paul@paul-moore.com>
---
 tests/lost_reset/test |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/lost_reset/test b/tests/lost_reset/test
index af82f0b..054e1e0 100755
--- a/tests/lost_reset/test
+++ b/tests/lost_reset/test
@@ -57,7 +57,7 @@ for ( $i = 0 ; $i < $iterations ; $i++ ) {    # iteration count
 
     # Add rule to generate audit queue events from floodping
     $result =
-      system("auditctl -a exit,always -S all -F pid=$ping_pid >/dev/null 2>&1");
+      system("auditctl -a exit,always -S all >/dev/null 2>&1");
 
     my $counter = 0;
     my $timeout = 50;
@@ -82,7 +82,7 @@ for ( $i = 0 ; $i < $iterations ; $i++ ) {    # iteration count
     }
 
     kill 'TERM', $ping_pid;
-    system("auditctl -d exit,always -S all -F pid=$ping_pid >/dev/null 2>&1");
+    system("auditctl -d exit,always -S all >/dev/null 2>&1");
 
     # Restart the daemon to collect messages in the log
     system("service auditd start >/dev/null 2>&1");

             reply	other threads:[~2018-12-13 23:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 23:17 Paul Moore [this message]
2018-12-13 23:23 ` [RFC PATCH] audit-testsuite: improve our chances of losing records in lost_reset Paul Moore
2018-12-14  1:59   ` Richard Guy Briggs
2018-12-14 15:53     ` Paul Moore
2018-12-14 16:12       ` Richard Guy Briggs
2018-12-14 20:35         ` Paul Moore
2018-12-14 21:00           ` Richard Guy Briggs
2018-12-15 17:35             ` Ondrej Mosnacek

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=154474302167.32049.14827507134973529836.stgit@chester \
    --to=paul@paul-moore.com \
    --cc=linux-audit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.