From: Paul Moore <pmoore@redhat.com>
To: sedat.dilek@gmail.com
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Guenter Roeck <linux@roeck-us.net>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-audit@redhat.com, rgb@redhat.com, sd@queasysnail.net,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] Overhaul the audit filename handling
Date: Mon, 26 Jan 2015 10:52:49 -0500 [thread overview]
Message-ID: <1670043.82pCAlqBeA@sifl> (raw)
In-Reply-To: <CA+icZUWOkW-ujARrnT4T3wsZh0EbkHR+p2q2c1-zJYKtP46hfA@mail.gmail.com>
On Saturday, January 24, 2015 10:03:06 AM Sedat Dilek wrote:
> I have tested vfs.git#getname2 on top of Linux v3.19-rc5-184-gc4e00f1
> (plus block-loopmq patchset) and it boots fine on Ubuntu/precise
> amd64.
Great, thank you for the additional testing.
> Just curious, where will this audit-filename-handling overhaul go through?
> Through Paul's audit-next or Al's vfs-next tree?
Al wanted to carry the patchset so that is where it lives now, you should see
it arrive in Linus' tree via the VFS tree.
--
paul moore
security @ redhat
next prev parent reply other threads:[~2015-01-26 15:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 4:59 [PATCH v2 0/5] Overhaul the audit filename handling Paul Moore
2015-01-22 4:59 ` [PATCH v2 1/5] fs: rework getname_kernel to handle up to PATH_MAX sized filenames Paul Moore
2015-01-22 15:53 ` Richard Guy Briggs
2015-01-22 16:56 ` Guenter Roeck
2015-01-22 5:00 ` [PATCH v2 2/5] fs: create proper filename objects using getname_kernel() Paul Moore
2015-01-22 15:54 ` Richard Guy Briggs
2015-01-22 5:00 ` [PATCH v2 3/5] audit: enable filename recording via getname_kernel() Paul Moore
2015-01-22 5:00 ` Paul Moore
2015-01-22 5:00 ` [PATCH v2 4/5] audit: fix filename matching in __audit_inode() and __audit_inode_child() Paul Moore
2015-01-22 16:04 ` Richard Guy Briggs
2015-01-22 5:00 ` [PATCH v2 5/5] audit: replace getname()/putname() hacks with reference counters Paul Moore
2015-01-22 16:09 ` Richard Guy Briggs
2015-01-22 16:24 ` Paul Moore
2015-01-22 5:36 ` [PATCH v2 0/5] Overhaul the audit filename handling Guenter Roeck
2015-01-22 7:54 ` Al Viro
2015-01-22 16:23 ` Paul Moore
2015-01-22 21:25 ` Paul Moore
2015-01-22 21:29 ` Al Viro
2015-01-22 21:40 ` Al Viro
2015-01-22 22:05 ` Paul Moore
2015-01-23 5:30 ` Al Viro
2015-01-23 16:15 ` Paul Moore
2015-01-24 9:03 ` Sedat Dilek
2015-01-24 22:54 ` Stephen Rothwell
2015-01-26 15:52 ` Paul Moore [this message]
2015-01-22 17:13 ` Guenter Roeck
2015-01-22 16:22 ` Paul Moore
2015-01-22 16:58 ` Guenter Roeck
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=1670043.82pCAlqBeA@sifl \
--to=pmoore@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rgb@redhat.com \
--cc=sd@queasysnail.net \
--cc=sedat.dilek@gmail.com \
--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.