From: Tony Jones <tonyj@suse.de>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com, Amy Griffis <amy.griffis@hp.com>,
chrisw@sous-sol.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 9/11] security: AppArmor - Audit changes
Date: Fri, 21 Apr 2006 17:19:14 -0700 [thread overview]
Message-ID: <20060422001914.GA9257@suse.de> (raw)
In-Reply-To: <200604212013.52374.sgrubb@redhat.com>
On Fri, Apr 21, 2006 at 08:13:52PM -0400, Steve Grubb wrote:
> On Friday 21 April 2006 17:21, Amy Griffis wrote:
> > linux-audit (cc'd) will likely want to review these changes.
>
> Yes, I second that. Tony, please cc audit patches to linux-audit mail list so
> we can see them. That said, I did tell Tony they could use message type
> numbers 1500 - 1600 for AppArmor if they need it.
Sorry, I thought I'd bounced this one patch in the series to the audit list.
I meant to. One more thing lost in the noise. Apologies.
1500 should already be reserved for apparmor userside. Only change is to
enable it kernelside plus of course the one more symbol export to bloat the
kernel image. Export of the vformat call is to make it analagous to vprintk.
Sometimes it's more convenient to have a single point of logging (as we do)
and you need to log data which is in va_list format.
Tony
prev parent reply other threads:[~2006-04-22 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060419174905.29149.67649.sendpatchset@ermintrude.int.wirex.com>
[not found] ` <20060419175018.29149.391.sendpatchset@ermintrude.int.wirex.com>
2006-04-21 21:21 ` [RFC][PATCH 9/11] security: AppArmor - Audit changes Amy Griffis
2006-04-22 0:13 ` Steve Grubb
2006-04-22 0:19 ` Tony Jones [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=20060422001914.GA9257@suse.de \
--to=tonyj@suse.de \
--cc=amy.griffis@hp.com \
--cc=chrisw@sous-sol.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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