public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Eric Paris <eparis@redhat.com>,
	linux-audit@redhat.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Audit fixes for 3.18
Date: Wed, 12 Nov 2014 23:19:11 -0500	[thread overview]
Message-ID: <4297973.SuVNDTyoQA@sifl> (raw)

Hi Linus,

After he sent the initial audit pull request for 3.18, Eric asked me to take 
over the management of the audit tree, hence this pull request to fix a couple 
of problems with audit.  As you can see below, the changes are minimal: adding 
some whitespace to a string so userspace parses it correctly, and fixing a 
problem with audit's usage of fsnotify that was causing audit watch rules to 
be lost.  Neither of these patches were very controversial on the mailing 
lists and they fix real problems, getting them into 3.18 would be a good 
thing.

As of about ten minutes ago, the audit tree applied cleanly on top of your 
tree.

Thanks,
-Paul

---
The following changes since commit 2991dd2b0117e864f394c826af6df144206ce0db:

  audit: rename audit_log_remove_rule to disambiguate for trees (2014-10-10 
15:30:25 -0400)

are available in the git repository at:

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

for you to fetch changes up to 799b601451b21ebe7af0e6e8f6e2ccd4683c5064:

  audit: keep inode pinned (2014-11-11 14:20:22 -0500)

----------------------------------------------------------------
Miklos Szeredi (1):
      audit: keep inode pinned

Richard Guy Briggs (1):
      audit: AUDIT_FEATURE_CHANGE message format missing delimiting space

 kernel/audit.c      | 2 +-
 kernel/audit_tree.c | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

-- 
paul moore
security and virtualization @ redhat

                 reply	other threads:[~2014-11-13  4:19 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=4297973.SuVNDTyoQA@sifl \
    --to=pmoore@redhat.com \
    --cc=eparis@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