archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <>
To: Linus Torvalds <>
Subject: [GIT PULL] audit/audit-pr-20240105
Date: Fri, 05 Jan 2024 18:20:52 -0500	[thread overview]
Message-ID: <> (raw)

Hi Linus,

I realize this is a little early, but my network access is expected to
be a little spotty the first half of next week so I wanted to get the
Linux v6.8 pull requests out now.  The audit PR is a fairly minor one
with only two patches:

* Send an audit ACK to userspace immediately upon receiving an auditd
registration event as opposed to waiting until the registration has
been fully processed and the audit backlog starts filling the netlink
buffers.  Sending the ACK earlier, as done in this PR, is still safe
as the operation should not fail at the point when the ACK is done,
and doing so helps avoid the ACK being dropped in extreme situations.

* Update the audit MAINTAINERS entry with additional information.
There isn't anything in this update that should be new to regular
contributors or list subscribers, but I'm pushing to start documenting
our processes, conventions, etc. and this seems like an important part
of that.


The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:

  Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)

are available in the Git repository at:

for you to fetch changes up to 4e8714b76613e6284b263274d6dddcfac24be262:

  MAINTAINERS: update the audit entry (2023-11-15 12:24:00 -0500)

audit/stable-6.8 PR 20240105

Chris Riches (1):
      audit: Send netlink ACK before setting connection in auditd_set

Paul Moore (1):
      MAINTAINERS: update the audit entry

 MAINTAINERS    |  6 +++++-
 kernel/audit.c | 31 ++++++++++++++++++++++++-------
 2 files changed, 29 insertions(+), 8 deletions(-)


             reply	other threads:[~2024-01-05 23:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 23:20 Paul Moore [this message]
2024-01-09 21:40 ` [GIT PULL] audit/audit-pr-20240105 pr-tracker-bot

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).