public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Audit patches for 4.6
Date: Thu, 17 Mar 2016 16:14:27 -0400	[thread overview]
Message-ID: <2010024.ZNtdp9huFu@sifl> (raw)

Hi Linus,

A small set of patches for audit this time; just three in total and one is a 
spelling fix.  The two patches with actual content are designed to help 
prevent new instances of auditd from displacing an existing, functioning 
auditd and to generate a log of the attempt.  Not to worry, dead/stuck auditd 
instances can still be replaced by a new instance without problem.

Nothing controversial, and everything passes our regression suite; please pull 
for Linux 4.6.

Thanks,
-Paul

---
The following changes since commit cb74ed278f8054fddf79ed930495b9e214f7c7b2:

  audit: always enable syscall auditing when supported and audit is enabled
         (2016-01-13 09:18:55 -0500)

are available in the git repository at:

  git://git.infradead.org/users/pcmoore/audit stable-4.6

for you to fetch changes up to fd97646b05957348e01be3d9de5c3d979b25c819:

  audit: Fix typo in comment (2016-02-08 11:25:39 -0500)

----------------------------------------------------------------
Richard Guy Briggs (2):
      audit: stop an old auditd being starved out by a new auditd
      audit: log failed attempts to change audit_pid configuration

Wei Yuan (1):
      audit: Fix typo in comment

 include/uapi/linux/audit.h |  1 +
 kernel/audit.c             | 20 +++++++++++++++++++-
 kernel/audit_watch.c       |  2 +-
 kernel/auditfilter.c       |  6 +++---
 4 files changed, 24 insertions(+), 5 deletions(-)

-- 
paul moore
security @ redhat

                 reply	other threads:[~2016-03-17 20:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2010024.ZNtdp9huFu@sifl \
    --to=pmoore@redhat.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