From: Paul Moore <pmoore@redhat.com>
To: linux-audit@redhat.com, viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] Overhaul the audit filename handling
Date: Mon, 12 Jan 2015 16:03:18 -0500 [thread overview]
Message-ID: <2809190.iPDDC9gGz8@sifl> (raw)
In-Reply-To: <20150108164514.11316.85331.stgit@localhost>
On Thursday, January 08, 2015 11:50:23 AM Paul Moore wrote:
> There have been some patches added to v3.19-rcX to fix various
> problems in the way audit handles filenames but they have been hacks
> on top of hacks, not really something we want long term. This
> patchset reworks the way audit handles filenames, removing a lot of
> nasty hacks added recently, and fixing a few bugs that still remain.
>
> Most significant to folks outside of audit, patch 5/5 does away with
> the nasty getname()/putname() kludge in favor of a less ugly reference
> count approach.
>
> Comments and feedback are welcome. If nothing ugly pops up on review
> I'll see if Linus is interested in taking this for the next v3.19-rcX
> release, otherwise I'll toss it into linux-next for v3.20.
>
> -Paul
>
> ---
>
> Paul Moore (5):
> fs: rework getname_kernel to handle up to PATH_MAX sized filenames
> fs: create proper filename objects using getname_kernel()
> audit: enable filename recording via getname_kernel()
> audit: fix filename matching in __audit_inode() and
> __audit_inode_child()
> audit: replace getname()/putname() hacks with reference counters
>
>
> fs/exec.c | 11 +++
> fs/namei.c | 98 ++++++++++++++++++-----------
> fs/open.c | 11 +++
> include/linux/audit.h | 3 -
> include/linux/fs.h | 9 +--
> kernel/audit.h | 17 +----
> kernel/auditsc.c | 167 ++++++++-------------------------------------
> 7 files changed, 115 insertions(+), 201 deletions(-)
Al/fs dev: any chance you guys can take a quick look at the fs relevant
portions of this patchset and give it a ACK/NACK? I'll carry the patchset in
the audit tree, but I'd like to see a thumbs up from someone in fs land before
I merge these patches.
Thanks,
-Paul
--
paul moore
security @ redhat
prev parent reply other threads:[~2015-01-12 21:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 16:50 [RFC PATCH 0/5] Overhaul the audit filename handling Paul Moore
2015-01-08 16:50 ` [RFC PATCH 1/5] fs: rework getname_kernel to handle up to PATH_MAX sized filenames Paul Moore
2015-01-14 21:02 ` Richard Guy Briggs
2015-01-08 16:50 ` [RFC PATCH 2/5] fs: create proper filename objects using getname_kernel() Paul Moore
2015-01-14 21:03 ` Richard Guy Briggs
2015-01-08 16:50 ` [RFC PATCH 3/5] audit: enable filename recording via getname_kernel() Paul Moore
2015-01-14 21:09 ` Richard Guy Briggs
2015-01-08 16:50 ` [RFC PATCH 4/5] audit: fix filename matching in __audit_inode() and __audit_inode_child() Paul Moore
2015-01-14 21:21 ` Richard Guy Briggs
2015-01-08 16:50 ` [RFC PATCH 5/5] audit: replace getname()/putname() hacks with reference counters Paul Moore
2015-01-14 21:37 ` Richard Guy Briggs
2015-01-14 21:45 ` Paul Moore
2015-01-12 21:03 ` Paul Moore [this message]
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=2809190.iPDDC9gGz8@sifl \
--to=pmoore@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.