From: Amy Griffis <amy.griffis@hp.com>
To: linux-audit@redhat.com
Cc: redhat-lspp@redhat.com
Subject: Re: Watch Performance
Date: Tue, 11 Apr 2006 12:11:41 -0400 [thread overview]
Message-ID: <20060411161141.GA16506@zk3.dec.com> (raw)
In-Reply-To: <200604110626.26843.sgrubb@redhat.com>
On Tue, Apr 11, 2006 at 06:26:26AM -0400, Steve Grubb wrote:
> On Monday 10 April 2006 23:51, Amy Griffis wrote:
> > 1) what audit rules did you use?
>
> I used the lspp rules to get the 1st 10, and the rest were against files
> in /etc/test.
I took a look at the rules lists in the tarball you sent. The rules
are not specified in a way that makes sense with what you are
measuring.
The watches are added with the -w syntax. In auditctl, this
translates to setting an "all" syscall rule.
> -w /etc/sysconfig/console
> -w /etc/sysconfig/pm
> -w /etc/sysconfig/system-config-users
> -w /etc/sysconfig/init
> -w /etc/sysconfig/hwconf
> -w /etc/sysconfig/netdump
> -w /etc/sysconfig/selinux
> -w /etc/sysconfig/hsqldb
> -w /etc/sysconfig/system-config-securitylevel
> -w /etc/sysconfig/mouse
> -w /etc/sysconfig/saslauthd.rpmnew
> -w /etc/sysconfig/netdump_id_dsa.pub
> -w /etc/sysconfig/clock
> -w /etc/sysconfig/grub
> -w /etc/sysconfig/wpa_supplicant
> ...
So for your worst-case, you have added 80 syscall rules that apply to
the access system call. It is not surprising that this would
significantly affect the performance of access().
IIRC, these rules were supposed to apply to watches.
> -a entry,possible -S chmod -S fchmod -S chown -S fchown -S lchown
> -a entry,possible -S creat -S open -S truncate -S ftruncate
> -a entry,possible -S mkdir -S rmdir
> -a entry,possible -S unlink -S rename -S link -S symlink
In the present implementation, the equivalent to the above groups is
(per each watch):
-a exit,always -S chmod -S fchmod -S chown -S fchown -S lchown
-S creat -S open -S truncate -S ftruncate -S mkdir -S rmdir -S unlink
-S rename -S link -S symlink -F watch=/etc/sysconfig/console
Now you don't have any rules for access(), so using it as the test
case is much more interesting.
> -a entry,always -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr
> -a entry,always -S mknod
> -a entry,always -S mount
> -a entry,always -S adjtimex -S settimeofday
Ideally, these would be a single rule.
> > 2) what system call(s) did you measure?
>
> access("/usr/include", 0);
>
> The watch rules were never triggered because I wanted to measure the overhead
> where no audit events occur. The syscall exercises the file system without
> doing any IO, which would complicate things, too.
>
> -Steve
>
next prev parent reply other threads:[~2006-04-11 16:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 16:21 Watch Performance Steve Grubb
2006-04-09 19:48 ` Steve Grubb
2006-04-11 13:12 ` Steve Grubb
2006-04-11 3:51 ` Amy Griffis
2006-04-11 10:26 ` Steve Grubb
2006-04-11 16:11 ` Amy Griffis [this message]
2006-04-11 21:01 ` Steve Grubb
2006-04-11 21:21 ` Linda Knippers
2006-04-12 21:15 ` Amy Griffis
2006-04-17 15:27 ` Timothy R. Chavez
2006-04-17 20:06 ` Klaus Weidner
2006-04-21 15:01 ` Amy Griffis
2006-04-21 15:13 ` Steve Grubb
2006-04-21 15:10 ` Linda Knippers
2006-04-21 16:07 ` Alexander Viro
2006-04-24 15:34 ` Amy Griffis
2006-05-10 15:32 ` Steve Grubb
2006-05-10 16:34 ` Alexander Viro
2006-05-10 19:23 ` Steve Grubb
2006-05-10 19:37 ` Alexander Viro
2006-05-10 19:51 ` 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=20060411161141.GA16506@zk3.dec.com \
--to=amy.griffis@hp.com \
--cc=linux-audit@redhat.com \
--cc=redhat-lspp@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