From: Richard Guy Briggs <rgb@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-audit@redhat.com
Subject: Re: [RFC PATCH] audit-testsuite: improve our chances of losing records in lost_reset
Date: Thu, 13 Dec 2018 20:59:38 -0500 [thread overview]
Message-ID: <20181214015938.rt7ufdgiu5jkvgxh@madcap2.tricolour.ca> (raw)
In-Reply-To: <CAHC9VhSqecrUDgyAhyt3qznGMsd-EF8m7F4VU=AXV5mZ2gjExA@mail.gmail.com>
On 2018-12-13 18:23, Paul Moore wrote:
> On Thu, Dec 13, 2018 at 6:17 PM Paul Moore <paul@paul-moore.com> wrote:
> > 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.
> >
> > tests/lost_reset/test | 4 ++--
>
> This resolves a problem I've been seeing with a fairly stubborn
> system. I would be very curious to hear if any others were
> experiencing problems with the lost_reset that this patch resolves.
This saddistic test would have brought the system to its knees before
the queue rework. This still works fine on my system, so this is
progress. I suspect that something weird was going on with your test
such that it wasn't getting the right PID. I don't know how this is
possible, but I have seen this same thing recently on the FUSE umount2
test where I needed to bump up the PID by one to catch the right task.
> paul moore
next prev parent reply other threads:[~2018-12-14 1:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 23:17 [RFC PATCH] audit-testsuite: improve our chances of losing records in lost_reset Paul Moore
2018-12-13 23:23 ` Paul Moore
2018-12-14 1:59 ` Richard Guy Briggs [this message]
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=20181214015938.rt7ufdgiu5jkvgxh@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=paul@paul-moore.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.