From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Richard Guy Briggs <rgb@redhat.com>
Subject: Re: [PATCH] audit: allow unlimited backlog queue
Date: Wed, 15 Jan 2014 08:03:11 -0500 [thread overview]
Message-ID: <2007730.kZnoD1RoCs@x2> (raw)
In-Reply-To: <20140114230432.GG23577@madcap2.tricolour.ca>
On Tuesday, January 14, 2014 06:04:32 PM Richard Guy Briggs wrote:
> On 14/01/14, Richard Guy Briggs wrote:
> > Since audit can already be disabled by "audit=0" on the kernel boot line,
> > or by the command "auditctl -e 0", it would be more useful to have the
> > audit_backlog_limit set to zero mean effectively unlimited (limited only
> > by system resources).
> >
> > These are userspace source code documentation changes in what's going in
> > upstream. See:
> > audit: allow unlimited backlog queue
> > git://toccata2.tricolour.ca/linux-2.6-rgb.git
> > https://lkml.org/lkml/2013/10/22/356
> > https://www.redhat.com/archives/linux-audit/2013-October/msg00029.html
>
> And this is a related BZ:
> https://bugzilla.redhat.com/show_bug.cgi?id=999756
This patch doesn't make sense in that context either. The problem is systemd
floods the audit system before auditd comes up. This begs the question of
whether auditd is being started early enough.
One solution from that bz is to make a boot time config option. Problem is,
everyone that really cares about audit will have to set that. So that means
the default should be bumped up. However, the bz mentions that embedded
systems don't like that. So, why not make a compile time config option that
keeps the current default (64) and server/desktop distributions can make that
512? You can even provide a boot time config so that people with really busy
systems can make it bigger if they choose.
Making 0 mean unlimited won't help embedded systems.
-Steve
next prev parent reply other threads:[~2014-01-15 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 22:59 [PATCH] audit: allow unlimited backlog queue Richard Guy Briggs
2014-01-14 23:04 ` Richard Guy Briggs
2014-01-15 13:03 ` Steve Grubb [this message]
2014-01-15 16:46 ` Richard Guy Briggs
2014-01-15 16:57 ` Steve Grubb
2014-01-15 17:12 ` Richard Guy Briggs
2014-01-15 17:24 ` Steve Grubb
2014-01-15 17:31 ` Richard Guy Briggs
2014-01-15 1:19 ` Gao feng
2014-01-15 12:53 ` Steve Grubb
2014-01-15 16:50 ` 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=2007730.kZnoD1RoCs@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.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