linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Alan Evangelista <alan.vitor@gmail.com>
Cc: Linux-Audit Mailing List <linux-audit@redhat.com>
Subject: Re: Backlog not working with kernel 3.10
Date: Wed, 17 Mar 2021 15:46:00 -0400	[thread overview]
Message-ID: <CAHC9VhRt+yK-JZQ13q9EWkYzen=+brbg55F79FxvjVKacjNgiw@mail.gmail.com> (raw)
In-Reply-To: <CAKz+TUuddR_Ohb+VUQMT=t3ajCPZ4PKdpteKuVcN4UDGqGrt=g@mail.gmail.com>

On Wed, Mar 17, 2021 at 4:41 AM Alan Evangelista <alan.vitor@gmail.com> wrote:
> PM> The audit queue mechanism (backlog) was pretty messed up in older
> kernels, and while we've fixed it in modern kernels, I believe that
> not all of the changes have been backported to the older distribution
> kernels.
>
> Do you know in which kernel version this mechanism was fixed?
> This information would help me decide which distro I should move to.

Ignoring any backporting that may have taken place, I believe all of
the critical patches were present in Linux v4.13 with a few
nice-to-have patches in v4.15.

-- 
paul moore
www.paul-moore.com

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


  reply	other threads:[~2021-03-17 19:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 21:25 Backlog not working with kernel 3.10 Alan Evangelista
2021-03-16 21:58 ` Paul Moore
2021-03-17  8:40   ` Alan Evangelista
2021-03-17 19:46     ` Paul Moore [this message]
2021-03-17  1:46 ` Richard Guy Briggs
     [not found]   ` <CAKz+TUsv2p3RM-Em=w3fcMP8ANQZt-H=NOMAxudGhNgjDWLRrw@mail.gmail.com>
2021-03-17  8:36     ` Fwd: " Alan Evangelista
2021-03-17 14:32   ` Lenny Bruzenak
2021-03-17 16:06     ` Richard Guy Briggs
2021-03-17 16:03 ` Richard Guy Briggs
2021-03-17 20:56   ` Alan Evangelista
2021-03-18  1:16 ` 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='CAHC9VhRt+yK-JZQ13q9EWkYzen=+brbg55F79FxvjVKacjNgiw@mail.gmail.com' \
    --to=paul@paul-moore.com \
    --cc=alan.vitor@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).