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 3.19
Date: Tue, 09 Dec 2014 21:35:48 -0500 [thread overview]
Message-ID: <2676941.D86tdbjuKD@sifl> (raw)
Hi Linus,
Two small patches from the audit next branch; only one of which has any real
significant code changes, the other is simply a MAINTAINERS update for audit.
The single code patch is pretty small and rather straightforward, it changes
the audit "version" number reported to userspace from an integer to a bitmap
which is used to indicate the functionality of the running kernel. This
really doesn't have much impact on the kernel, but it will make life easier
for the audit userspace folks. Thankfully we were still on a version number
which allowed us to do this without breaking userspace.
For what it is worth, as of a few minutes ago, the branch below applied
cleanly on top of your tree.
Thanks,
-Paul
---
The following changes since commit 799b601451b21ebe7af0e6e8f6e2ccd4683c5064:
audit: keep inode pinned (2014-11-11 14:20:22 -0500)
are available in the git repository at:
git://git.infradead.org/users/pcmoore/audit upstream
for you to fetch changes up to 0f7e94ee40d06f7a04e039392dfee8244bd8a7e0:
Merge branch 'next' into upstream for v3.19 (2014-12-09 14:38:30 -0500)
----------------------------------------------------------------
Paul Moore (2):
audit: add Paul Moore to the MAINTAINERS entry
Merge branch 'next' into upstream for v3.19
Richard Guy Briggs (1):
audit: convert status version to a feature bitmap
MAINTAINERS | 5 +++--
include/uapi/linux/audit.h | 17 +++++++++++++----
kernel/audit.c | 2 +-
3 files changed, 17 insertions(+), 7 deletions(-)
reply other threads:[~2014-12-10 2:35 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=2676941.D86tdbjuKD@sifl \
--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).