From: Chris Wright <chrisw@osdl.org>
To: Atul Sabharwal <atul_sabharwal@linux.jf.intel.com>
Cc: linux-kernel@vger.kernel.org, atul.sabharwal@intel.com
Subject: Re: [Announce] Non Invasive Kernel Monitor for threads/processes
Date: Tue, 15 Jun 2004 17:39:51 -0700 [thread overview]
Message-ID: <20040615173951.E22989@build.pdx.osdl.net> (raw)
In-Reply-To: <40CF4233.70709@linux.jf.intel.com>; from atul_sabharwal@linux.jf.intel.com on Tue, Jun 15, 2004 at 11:38:43AM -0700
* Atul Sabharwal (atul_sabharwal@linux.jf.intel.com) wrote:
> We have been working with a solution for non-intrusively trapping on lifetime
> of processes/threads. This is useful for management applications running in
> telecom and enterprise data centers that need to monitor a set of threads/
> processes.
>
> Project Goal::
> ~~~~~~~~~~~~~~
> To create a kernel patch that shall support methods to non-intrusively monitor
> processes/threads at the kernel level. It would use a notfication mechanism in
> the kernel that allows registration of events of interest regarding processes/
> threads. Events of interest could be the following : Process creation (fork),
> Process exit(exit), Process calls(exec), thread creation & thread exit.
These spots are already hooked via LSM and audit (the latter is capable
of communicating such events to userspace via netfilter) Was that not
sufficient somehow? In fact, the netfilter queuing will probably fair
better than sigqueue which fairly limited. Might be worth looking into
that. Did you look at the task ornament patch floating about from David
Howells? If new code is needed, that patch looks more generically useful.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-06-16 0:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2004-06-16 12:32 ` Karim Yaghmour
2004-06-15 22:48 Sabharwal, Atul
2004-06-16 0:54 Sabharwal, Atul
2004-06-16 1:12 ` Chris Wright
2004-06-16 14:28 ` Chris Friesen
2004-06-16 17:36 ` Rusty Lynch
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=20040615173951.E22989@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=atul.sabharwal@intel.com \
--cc=atul_sabharwal@linux.jf.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®