From: Chris Wright <chrisw@osdl.org>
To: "Sabharwal, Atul" <atul.sabharwal@intel.com>
Cc: Chris Wright <chrisw@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [Announce] Non Invasive Kernel Monitor for threads/processes
Date: Tue, 15 Jun 2004 18:12:30 -0700 [thread overview]
Message-ID: <20040615181230.V21045@build.pdx.osdl.net> (raw)
In-Reply-To: <66539F0E7F15B44C9C0FC50D0FF024F7B1A324@orsmsx407>; from atul.sabharwal@intel.com on Tue, Jun 15, 2004 at 05:54:40PM -0700
* Sabharwal, Atul (atul.sabharwal@intel.com) wrote:
>
> How does auditing work in the event of a process failure ? There would
> be
> no system call triggered in that case. Also, my initial thoughts are
Correct. Currently the main audit user is selinux, which gets
indication of the process death from LSM.
> that the non-invasive Kmonitor is lesser performance impact when
> compared
> to auditing. I would spend some time developing sample code to confirm
> it.
Yes it's possible, but the audit context is per task, and can be
filtered per task, so overhead should only effect the tasks you care
about.
> I have not looked at the task ornament patch. If you could send me a
> link.
I have nothing more recent than you'll find in google, sorry.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-06-16 1:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 0:54 Sabharwal, Atul
2004-06-16 1:12 ` Chris Wright [this message]
2004-06-16 14:28 ` Chris Friesen
2004-06-16 17:36 ` Rusty Lynch
-- strict thread matches above, loose matches on Subject: below --
2004-06-15 22:48 Sabharwal, Atul
2004-06-15 18:38 Atul Sabharwal
2004-06-15 19:54 ` Atul Sabharwal
[not found] ` <40CF5D39.1060701@linux.jf.intel.com>
[not found] ` <20040615142304.5d9591d5.akpm@osdl.org>
2004-06-16 0:25 ` Atul Sabharwal
2004-06-16 1:01 ` Rusty Lynch
2004-06-16 0:39 ` Chris Wright
2004-06-16 12:32 ` Karim Yaghmour
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=20040615181230.V21045@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=atul.sabharwal@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®