netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: latten@austin.ibm.com
Cc: netdev@vger.kernel.org, linux-audit@redhat.com, sgrubb@redhat.com
Subject: Re: [PATCH] improved xfrm_audit_log() patch
Date: Thu, 23 Aug 2007 13:07:30 -0700 (PDT)	[thread overview]
Message-ID: <20070823.130730.40743564.davem@davemloft.net> (raw)
In-Reply-To: <1187889310.15699.735.camel@faith.austin.ibm.com>

From: Joy Latten <latten@austin.ibm.com>
Date: Thu, 23 Aug 2007 12:15:10 -0500

> For example, when auditing the addition of a policy, either
> xfrm_user_audit_policy_add(xp, result, skb) or
> pfkey_audit_policy_add(xp, result) will get called. 
> I need two because xfrm_user gets loginuid/secid from netlink/skb
> and pfkey gets it from audit_get_loginuid(). 
> Each will setup and format audit buffer according
> to what they want.
> 
> Also, for deleting, there will be pfkey_audit_policy_delete(xp, result)
> and xfrm_user_audit_policy_delete(xp, result, skb).

This sounds great.

How cheap is the "auditing enabled" test?  Perhaps it can
be even inlined into the xfrm audit hooks.

  reply	other threads:[~2007-08-23 20:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 16:16 [PATCH] improved xfrm_audit_log() patch Joy Latten
2007-08-21  7:24 ` David Miller
2007-08-22 19:51   ` David Miller
2007-08-23  1:29     ` Joy Latten
2007-08-23  3:05       ` David Miller
2007-08-23 17:15         ` Joy Latten
2007-08-23 20:07           ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-02 20:56 Joy Latten
2007-08-08  1:32 ` David Miller

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=20070823.130730.40743564.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=latten@austin.ibm.com \
    --cc=linux-audit@redhat.com \
    --cc=netdev@vger.kernel.org \
    --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).