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 fixes for 3.19
Date: Tue, 23 Dec 2014 18:10:03 -0500 [thread overview]
Message-ID: <1426990.sj1Az20XEf@sifl> (raw)
Hi Linus,
Four patches to fix various problems with the audit subsystem, all are fairly
small and straightforward. One patch fixes a problem where we weren't using
the correct gfp allocation flags (GFP_KERNEL regardless of context, oops), one
patch fixes a problem with old userspace tools (this was broken for a while),
one patch fixes a problem where we weren't recording pathnames correctly, and
one fixes a problem with PID based filters. In general I don't think there is
anything controversial with this patchset, and it fixes some rather
unfortunate bugs; the allocation flag one can be particularly scary looking
for users. Please pull for the next v3.19-rcX.
Thanks,
-Paul
---
The following changes since commit 0f7e94ee40d06f7a04e039392dfee8244bd8a7e0:
Merge branch 'next' into upstream for v3.19 (2014-12-09 14:38:30 -0500)
are available in the git repository at:
git://git.infradead.org/users/pcmoore/audit upstream
for you to fetch changes up to 041d7b98ffe59c59fdd639931dea7d74f9aa9a59:
audit: restore AUDIT_LOGINUID unset ABI (2014-12-23 16:40:18 -0500)
----------------------------------------------------------------
Paul Moore (2):
audit: don't attempt to lookup PIDs when changing PID filtering audit
rules
audit: correctly record file names with different path name types
Richard Guy Briggs (2):
audit: use supplied gfp_mask from audit_buffer in
kauditd_send_multicast_skb
audit: restore AUDIT_LOGINUID unset ABI
include/linux/audit.h | 4 ++++
kernel/audit.c | 8 ++++----
kernel/auditfilter.c | 23 ++++++++++-------------
kernel/auditsc.c | 14 ++++++++++----
4 files changed, 28 insertions(+), 21 deletions(-)
reply other threads:[~2014-12-23 23:10 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=1426990.sj1Az20XEf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.