linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Audit patches for v5.9
Date: Mon, 3 Aug 2020 21:00:01 -0400	[thread overview]
Message-ID: <CAHC9VhRP3yN4dvrEe5_iAgVDnLNeedLOLXeb_zaE9OmBW_qSQw@mail.gmail.com> (raw)

Hi Linus,

Here are the audit patches for the v5.9 merge window.  All of the
patches in this pull request pass our test suite and merged cleanly
with your tree from a few hours ago.

Aside from some smaller bug fixes, here are the highlights:

- Add a new backlog wait metric to the audit status message, this is
intended to help admins determine how long processes have been waiting
for the audit backlog queue to clear

- Generate audit records for nftables configuration changes

- Generate CWD audit records for for the relevant LSM audit records

Please merge for v5.9, thanks,
-Paul

--
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:

 Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)

are available in the Git repository at:

 git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git
   tags/audit-pr-20200803

for you to fetch changes up to b43870c74f3fdf0cd06bf5f1b7a5ed70a2cd4ed2:

 audit: report audit wait metric in audit status reply
   (2020-07-21 11:21:44 -0400)

----------------------------------------------------------------
audit/stable-5.9 PR 20200803

----------------------------------------------------------------
Gustavo A. R. Silva (1):
     audit: Use struct_size() helper in alloc_chunk

Max Englander (1):
     audit: report audit wait metric in audit status reply

Paul Moore (1):
     audit: use the proper gfp flags in the audit_log_nfcfg() calls

Richard Guy Briggs (5):
     audit: log nftables configuration change events
     audit: add gfp parameter to audit_log_nfcfg
     audit: remove unused !CONFIG_AUDITSYSCALL __audit_inode* stubs
     audit: issue CWD record to accompany LSM_AUDIT_DATA_* records
     audit: purge audit_log_string from the intra-kernel audit API

include/linux/audit.h           |  46 +++++++++++------
include/uapi/linux/audit.h      |  18 ++++---
kernel/audit.c                  |  39 +++++++++-----
kernel/audit_tree.c             |   4 +-
kernel/auditsc.c                |  45 +++++++++++++---
net/bridge/netfilter/ebtables.c |   6 +--
net/netfilter/nf_tables_api.c   | 112 ++++++++++++++++++++++++++++++++++++
net/netfilter/x_tables.c        |   5 +-
security/apparmor/audit.c       |  10 ++--
security/apparmor/file.c        |  25 +++------
security/apparmor/ipc.c         |  46 ++++++++---------
security/apparmor/net.c         |  14 ++---
security/lsm_audit.c            |   9 +++-
13 files changed, 273 insertions(+), 106 deletions(-)

-- 
paul moore
www.paul-moore.com

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


             reply	other threads:[~2020-08-04  1:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  1:00 Paul Moore [this message]
2020-08-04 21:40 ` [GIT PULL] Audit patches for v5.9 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:
  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=CAHC9VhRP3yN4dvrEe5_iAgVDnLNeedLOLXeb_zaE9OmBW_qSQw@mail.gmail.com \
    --to=paul@paul-moore.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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).