From: Steve Grubb <sgrubb@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] audit: optionally print warning after waiting to enqueue record
Date: Thu, 18 Jun 2020 10:36:43 -0400 [thread overview]
Message-ID: <8359651.kEV6mM8lSS@x2> (raw)
In-Reply-To: <CAHC9VhRVk0OtY=r9iKyVmJJX6m4+oWWV0=idy-FOS9zOszMcKQ@mail.gmail.com>
On Thursday, June 18, 2020 9:46:54 AM EDT Paul Moore wrote:
> On Thu, Jun 18, 2020 at 9:39 AM Steve Grubb <sgrubb@redhat.com> wrote:
> > The kernel cannot grow the backlog unbounded. If you do nothing, the
> > backlog is 64 - which is too small to really use. Otherwise, you set the
> > backlog to a finite number with the -b option.
>
> If one were to set the backlog limit to 0, it is effectively disabled
> allowing the backlog to grow without any restrictions placed on it by
> the audit subsystem.
Then I'd say you asked for it. The cure is setting a number. But regardless,
we could use some metrics on the backlog and visibility into the time it
takes to dequeue. That might signal problems with plugins or overly agressive
rules.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2020-06-18 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 4:58 [PATCH] audit: optionally print warning after waiting to enqueue record Max Englander
2020-06-17 18:47 ` Paul Moore
2020-06-17 22:54 ` Max Englander
2020-06-18 1:06 ` Paul Moore
2020-06-18 23:48 ` Max Englander
2020-06-19 0:30 ` Richard Guy Briggs
2020-06-24 0:15 ` Paul Moore
2020-06-25 3:34 ` Max Englander
2020-06-18 13:39 ` Steve Grubb
2020-06-18 13:46 ` Paul Moore
2020-06-18 14:36 ` Steve Grubb [this message]
2020-06-18 16:29 ` Paul Moore
2020-06-18 22:57 ` Max Englander
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=8359651.kEV6mM8lSS@x2 \
--to=sgrubb@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.