LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-fsdevel@vger.kernel.org, linux-audit@redhat.com,
	rgb@redhat.com, sd@queasysnail.net, linux-kernel@vger.kernel.org,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH v2 0/5] Overhaul the audit filename handling
Date: Thu, 22 Jan 2015 11:22:43 -0500	[thread overview]
Message-ID: <3252765.lrITUkIS9l@sifl> (raw)
In-Reply-To: <54C08C62.8010609@roeck-us.net>

On Wednesday, January 21, 2015 09:36:34 PM Guenter Roeck wrote:
> On 01/21/2015 08:59 PM, Paul Moore wrote:
> > This patchset has some important changes from the previous revision,
> > namely a fix from Al Viro (included in 2/5) that resolves a boot panic
> > on some systems as well as some smaller, less noteworthy fixes found
> > in the linux-next announcement thread from January 20th (refcount bump
> > in __audit_reusename() and a inode type in __audit_inode()).
> > 
> > This patchset still needs some additional testing to verify that the
> > audit code still functions properly (the minor fixes mentioned above)
> > and there is an additional patch from Al that should be included as
> > well, but I wanted to post this and push the series to the audit next
> > branch quickly since a number of folks were affected by the boot panic.
> > 
> > ---
> > 
> > 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
> 
> Hi Paul,
> 
> What is the baseline for this patch set ? Obviously -next won't work,
> and it does not apply to mainline either.

This patchset currently lives, along with one other unrelated patch, in the 
audit next branch:

 * git://git.infradead.org/users/pcmoore/audit

I'm currently testing these in combination with the patch Al posted last 
night.  Assuming all goes well I'll drop them from the audit next branch and 
toss all six patches (these plus Al's) into another branch in case Al wants to 
pull them for the VFS tree.

-- 
paul moore
security @ redhat


  parent reply	other threads:[~2015-01-22 16:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  4:59 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 ` [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
2015-01-22 17:13     ` Guenter Roeck
2015-01-22 16:22   ` Paul Moore [this message]
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=3252765.lrITUkIS9l@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=viro@zeniv.linux.org.uk \
    --subject='Re: [PATCH v2 0/5] Overhaul the audit filename handling' \
    /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

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).