Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Bigonville <bigon@debian.org>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-audit@redhat.com
Subject: Re: kauditd hold queue overflow in 4.11
Date: Sat, 9 Sep 2017 12:02:02 +0200	[thread overview]
Message-ID: <48bc9489-0b06-e136-4545-5702e21e992c@debian.org> (raw)
In-Reply-To: <CAHC9VhToz6oKgvHfO-zHOKvYpAnQmP+RHZRVzdVwE_DVL3egqA@mail.gmail.com>

Le 11/07/17 à 00:23, Paul Moore a écrit :
> On Mon, Jul 10, 2017 at 4:01 PM, Laurent Bigonville <bigon@debian.org> wrote:
>> Le 10/07/17 à 18:00, Paul Moore a écrit :
>>
>>> On Mon, Jul 10, 2017 at 10:59 AM, Laurent Bigonville <bigon@debian.org>
>>> wrote:
>>>> Hi,
>>>>
>>>> With 4.11.6 (that has been uploaded in debian unstable) I get a lot of
>>>> messages in dmesg like
>>>>
>>>> [100052.120468] audit: audit_lost=66041 audit_rate_limit=0
>>>> audit_backlog_limit=8192
>>>> [100052.120470] audit: kauditd hold queue overflow
>>>>
>>>> And it also seems that the messages are not stored in auditd logs
>>>> anymore.
>>>>
>>>> https://git.kernel.org/linus/264d509637d95f9404e52ced5003ad352e0f6a26
>>>> seems
>>>> to be included in this release
>>>>
>>>> An idea?
>>> 7
>>> I'm going to assume that your backlog limit is set to a sane value for
>>> your system's configuration, so that leaves me with two commits that
>>> may be of interest:
>>>
>>> * 1df30f8264b8 ("audit: fix the RCU locking for the auditd_connection
>>> structure")
>>>
>>> This was a manual backport of a v4.12 patch to v4.11, looking now, I
>>> see it should be in +v4.11.5 so that probably isn't your problem ...
>>>
>>> * c81be52a3ac0 ("audit: fix a race condition with the auditd tracking
>>> code")
>>>
>>> This patch is relatively new and was just sent up to Linus during the
>>> next merge window; it's a race condition fix so reproducing it can be
>>> tricky, although it may be easily reproducible on your system at the
>>> moment (luck you!).  If you aren't in a position to apply the patch,
>>> the workaround is rather simple: restart auditd.
>>>
>>> If none of the above works, let me know, but I strongly suspect you're
>>> tripping over the race condition fixed in that last patch.
>>>
>> I didn't test the patch yet, but I restarted the auditd daemon 2 times and
>> after that the queue has been flushed and I got all the message since this
>> noon in the audit logs.
> That sounds right; I'm guessing the patch above should be a more permanent fix.
>

The patch should be applied in 4.13-rc7 right?

It seems to fix the main issue (all the audit messages being logged in 
dmesg) but I can still see from time to time the following message:

[   14.747565] audit: audit_lost=59 audit_rate_limit=0 audit_backlog_limit=64
[   14.747566] audit: kauditd hold queue overflow


--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2017-09-09 10:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 14:59 kauditd hold queue overflow in 4.11 Laurent Bigonville
2017-07-10 16:00 ` Paul Moore
2017-07-10 20:01   ` Laurent Bigonville
2017-07-10 22:23     ` Paul Moore
2017-09-09 10:02       ` Laurent Bigonville [this message]
2017-09-09 14:22         ` Steve Grubb
2017-09-09 20:41           ` Laurent Bigonville
2017-09-10  0:13             ` Steve Grubb
2017-09-09 14:35         ` Paul Moore

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=48bc9489-0b06-e136-4545-5702e21e992c@debian.org \
    --to=bigon@debian.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox