From: Eric Paris <eparis@parisplace.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jmorris@namei.org, vyekkirala@trustedcs.com,
cxzhang@watson.ibm.com, sds@tycho.nsa.gov
Subject: Re: [PATCH] Add xfrm policy change auditing to pfkey_spdget
Date: Thu, 08 Mar 2007 11:20:15 -0500 [thread overview]
Message-ID: <1173370815.31047.134.camel@localhost.localdomain> (raw)
In-Reply-To: <20070307.160740.77057241.davem@davemloft.net>
On Wed, 2007-03-07 at 16:07 -0800, David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Wed, 07 Mar 2007 15:43:16 -0800 (PST)
>
> > From: Eric Paris <eparis@parisplace.org>
> > Date: Fri, 02 Mar 2007 13:51:24 -0500
> >
> > > pfkey_spdget neither had an LSM security hook nor auditing for the
> > > removal of xfrm_policy structs. The security hook was added when it was
> > > moved into xfrm_policy_byid instead of the callers to that function by
> > > my earlier patch and this patch adds the auditing hooks as well.
> > >
> > > Signed-off-by: Eric Paris <eparis@redhat.com>
> >
> > Applied.
>
> This patch was missing an openning brace on the "if (delete)" line.
> Eric you don't post patches without at least compile testing
> them now do you? :-)
>
> I fixed this up, but I will just kick it back to you next time,
> and I will likely growl very loudly in your general direction
> too. ;)
I lose at using git. Sorry. I'll be more careful to check that all of
my changes on the current branch are committed before I run my git diff.
Or maybe someone will convince me to use git in an all new better way.
I created a branch that has your tree and then created a new branch off
of that for my changes. I checked out my branch made my patch and
commited. I then tried to compile failed and fixed it up. I then
compiled, booted, and tested. When I thought it was working I did a
git diff miller..my-branch-with-pfkey_spdget
which didn't have my fix up because i didn't commit it to my local
branch. Is there a better way to get a diff between my miller tree and
'everything in the branch I have checked out even if it is not
committed'?
Sorry, even if there are no ideas I'll be more careful.
-Eric
next prev parent reply other threads:[~2007-03-08 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 18:51 [PATCH] Add xfrm policy change auditing to pfkey_spdget Eric Paris
2007-03-05 15:59 ` Venkat Yekkirala
2007-03-06 0:37 ` James Morris
2007-03-07 23:43 ` David Miller
2007-03-08 0:07 ` David Miller
2007-03-08 16:20 ` Eric Paris [this message]
2007-03-08 17:12 ` James Morris
2007-03-08 20:08 ` Paul Moore
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=1173370815.31047.134.camel@localhost.localdomain \
--to=eparis@parisplace.org \
--cc=cxzhang@watson.ibm.com \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=vyekkirala@trustedcs.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).