From: Steve Grubb <sgrubb@redhat.com>
To: Marcelo Cerri <mhcerri@linux.vnet.ibm.com>
Cc: linux-audit@redhat.com, gcwilson@us.ibm.com, bryntcor@us.ibm.com
Subject: Re: [PATCH] auvirt: a new tool for reporting events related to virtual machines
Date: Wed, 11 Jan 2012 16:20:06 -0500 [thread overview]
Message-ID: <201201111620.06515.sgrubb@redhat.com> (raw)
In-Reply-To: <4F05D389.8090808@linux.vnet.ibm.com>
On Thursday, January 05, 2012 11:44:57 AM Marcelo Cerri wrote:
> But I'm not sure what means "anomaly events". Would it be malformed
> records (without some fields, for example) or a specific record type
> generated by the kernel or some other userspace application?
No, these are events in the range of AUDIT_FIRST_ANOM_MSG and
AUDIT_LAST_ANOM_MSG and some from the kernel in the range of
AUDIT_FIRST_KERN_ANOM_MSG and AUDIT_LAST_KERN_ANOM_MSG.
-Steve
next prev parent reply other threads:[~2012-01-11 21:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 15:56 [PATCH] auvirt: a new tool for reporting events related to virtual machines Marcelo Cerri
2011-12-20 18:18 ` Steve Grubb
2012-01-05 16:44 ` Marcelo Cerri
2012-01-09 17:00 ` Marcelo Cerri
2012-01-11 21:48 ` Steve Grubb
2012-01-13 17:25 ` Marcelo Cerri
2012-01-13 19:23 ` Steve Grubb
2012-01-13 19:45 ` Marcelo Cerri
2012-01-13 20:56 ` Steve Grubb
2012-01-16 13:05 ` Marcelo Cerri
2012-01-16 15:36 ` Steve Grubb
2012-01-11 21:20 ` Steve Grubb [this message]
2012-01-24 18:08 ` Marcelo Cerri
2012-01-24 18:33 ` Marcelo Cerri
2012-01-24 20:27 ` Steve Grubb
2012-01-25 12:56 ` Marcelo Cerri
2012-01-27 16:37 ` Marcelo Cerri
2012-01-27 17:21 ` Steve Grubb
2012-01-27 17:31 ` Marcelo Cerri
-- strict thread matches above, loose matches on Subject: below --
2012-02-01 17:16 Marcelo Cerri
2012-02-03 18:52 ` 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=201201111620.06515.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=bryntcor@us.ibm.com \
--cc=gcwilson@us.ibm.com \
--cc=linux-audit@redhat.com \
--cc=mhcerri@linux.vnet.ibm.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