linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
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 V9 2/3] audit: implement audit by executable
Date: Fri, 07 Aug 2015 10:27:30 -0400	[thread overview]
Message-ID: <1641279.1Xz85nn9bU@sifl> (raw)
In-Reply-To: <20150807062411.GB12116@madcap2.tricolour.ca>

On Friday, August 07, 2015 02:25:14 AM Richard Guy Briggs wrote:
> On 15/08/06, Paul Moore wrote:
>
> > Merged, although some more minor whitespace tweaks were necessary for
> > checkpatch.  On a related note, if you're not running
> > ./scripts/checlpatch.pl on your patches before sending them out, I would
> > recommend it.  It isn't perfect, but it can catch some silly things that
> > we all do from time to time.
>
> No excuses...  I have been running it pretty regularly and got lazy and
> distracted with patch revisions.  I can't say I agree with the no space
> before closing round parenthesis due to legibility, but will comply.

Okay, glad to hear you run it regularly when submitting patches.

I agree that there are some things I might change about the kernel's style 
choices, but I think it is more important that we remain consistent with the 
kernel as a whole.  I really like tools that enforce things like this, even if 
I don't agree 100% with the results.
 
> > Also, one last thing.  It is pretty late in the -rcX cycle to merge these
> > two patches, but considering that we've been talking about these for a
> > while, I'm reasonably okay merging them.  In the future, if it isn't in
> > audit#next by the time -rc5 is released, it isn't going to make the merge
> > window.
> 
> I've been quite aware of that looming merge window...  This feature has
> been iterating for a while, so there are no big surprises.  I was aiming
> for earlier.  :)

Well, I think it is a little early to say there are no big surprises, we won't 
know that for a few more weeks, but if we make it to -rc3/4 without any 
problems I'll breathe a bit easier ;)

-- 
paul moore
security @ redhat

  reply	other threads:[~2015-08-07 14:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 20:29 [PATCH V9 0/3] audit by executable name Richard Guy Briggs
2015-08-05 20:29 ` [PATCH V9 1/3] audit: clean simple fsnotify implementation Richard Guy Briggs
2015-08-06 20:19   ` Paul Moore
2015-08-05 20:29 ` [PATCH V9 2/3] audit: implement audit by executable Richard Guy Briggs
2015-08-06 20:23   ` Paul Moore
2015-08-07  6:25     ` Richard Guy Briggs
2015-08-07 14:27       ` Paul Moore [this message]
2015-08-05 20:29 ` [PATCH V9 3/3] audit: add audit by children of executable path Richard Guy Briggs
2015-08-06 20:24   ` Paul Moore
2015-08-06 21:08     ` Steve Grubb
2015-08-07  0:07       ` Paul Moore
2015-08-07  6:37         ` Richard Guy Briggs
2015-08-07 14:30           ` Paul Moore
2015-08-07 16:03             ` Richard Guy Briggs
2015-08-07 20:47               ` Paul Moore
2015-08-08  5:07                 ` Richard Guy Briggs

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=1641279.1Xz85nn9bU@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 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).