From: Paul Moore <pmoore@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org,
sgrubb@redhat.com, eparis@redhat.com, peter@hda3.com
Subject: Re: [PATCH V10] fixup! audit: add audit by children of executable path
Date: Mon, 10 Aug 2015 14:45:30 -0400 [thread overview]
Message-ID: <4771859.lgjRgQqjhi@sifl> (raw)
In-Reply-To: <20150810165354.GA15959@madcap2.tricolour.ca>
On Monday, August 10, 2015 12:53:54 PM Richard Guy Briggs wrote:
> On 15/08/10, Paul Moore wrote:
> > I'm still not convinced that we need to merge exe child filtering patch so
> > I'm not going to apply this, or your v10 patch, at this point in time.
> > If you want to hold on to the code in case you and/or Steve think you can
> > convince me at a later date, you might as well merge this fixup patch
> > into the v10 patch.
>
> I fixed the known problems and reposted it for reference and public
> archive so that it wasn't buried privately in my tree.
No problem, that's smart. I just wanted to respond so that there wasn't any
confusion about the status of this patch; I figure everybody who takes the
time to post a patch deserves a response, even if it is "no thanks".
> Aside from the need for the child filtering patch, do the RCU treatments
> here look reasonable?
Yep, it looks reasonable to me.
--
paul moore
security @ redhat
prev parent reply other threads:[~2015-08-10 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 14:23 [PATCH V10] fixup! audit: add audit by children of executable path Richard Guy Briggs
2015-08-10 16:27 ` Paul Moore
2015-08-10 16:53 ` Richard Guy Briggs
2015-08-10 18:45 ` 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=4771859.lgjRgQqjhi@sifl \
--to=pmoore@redhat.com \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hda3.com \
--cc=rgb@redhat.com \
--cc=sgrubb@redhat.com \
/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.