From: Steve Grubb <sgrubb@redhat.com>
To: Linux Audit <linux-audit@redhat.com>
Subject: RFC deprecating the possible action
Date: Mon, 10 Apr 2006 15:05:57 -0400 [thread overview]
Message-ID: <200604101505.57763.sgrubb@redhat.com> (raw)
Hi,
I was looking at the syscall entry code and was thinking that we could
eliminate the "possible" action. The code in syscall entry seems to have been
hard-wired such that every syscall performs the action as if "possible" was
set. (Unless a never rule evaluates true.)
Since this is now hard-wired into the code, I'd like to eliminate the action
so that people do not submit rules with "possible" as an action. This would
help in terms of performance since the system won't be evaluating rules that
are hard coded.
We currently have 5 syscall rules in the capp.rules file and lspp.rules file
that would be eliminated by this change. I could always delete them from the
rule file, but other people will make the mistake of setting possible on some
rules without studying the kernel code.
What's people's thoughts on this?
-Steve
next reply other threads:[~2006-04-10 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 19:05 Steve Grubb [this message]
2006-04-10 19:55 ` RFC deprecating the possible action Linda Knippers
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=200604101505.57763.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@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