From: Joy Latten <latten@austin.ibm.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, linux-audit@redhat.com
Subject: Re: [PATCH]: revised make xfrm_audit_log more generic patch
Date: Tue, 24 Jul 2007 11:17:58 -0500 [thread overview]
Message-ID: <1185293878.15699.358.camel@faith.austin.ibm.com> (raw)
In-Reply-To: <200707241104.56310.sgrubb@redhat.com>
On Tue, 2007-07-24 at 11:04 -0400, Steve Grubb wrote:
> > + audit_log_format(audit_buf, "%s: auid=%u", buf, auid);
> >
> > if (sid != 0 &&
> > security_secid_to_secctx(sid, &secctx, &secctx_len) == 0)
>
> The operation in buf will not be parsed by the user space tools. Let's
> use "op=%s " where you have "%s: " above. Audit record fields are name=value
> and fields separated by spaces. "op" is what we are using in other places to
> mean operation.
>
> I know its a change from the records above, but we previously had some detail
> about what operation was being performed by the record type and this did not
> matter so much. Now that we only have one event type, the meaning of the
> event being recorded needs to be parsable and in a field.
>
> It also wouldn't hurt to change the text being sent to this function to have a
> hyphen instead of a space, so "SPD delete" becomes "SPD-delete". This keeps
> the parser happy.
>
> This patch otherwise looks good.
Sounds good. I will make the changes and resend.
Thanks!!
Joy
next prev parent reply other threads:[~2007-07-24 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 21:46 [PATCH]: revised make xfrm_audit_log more generic patch Joy Latten
2007-07-23 22:27 ` James Morris
2007-07-24 15:04 ` Steve Grubb
2007-07-24 16:17 ` Joy Latten [this message]
2007-07-24 16:33 ` Joy Latten
2007-07-24 17:10 ` Steve Grubb
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=1185293878.15699.358.camel@faith.austin.ibm.com \
--to=latten@austin.ibm.com \
--cc=davem@davemloft.net \
--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