From: Rusty Lynch <rusty@linux.jf.intel.com>
To: faith@redhat.com
Cc: linux-kernel@vger.kernel.org, atul_sabharwal@linux.jf.intel.com
Subject: Re: [Announce] Non Invasive Kernel Monitor for threads/processes
Date: Tue, 15 Jun 2004 18:01:04 -0700 [thread overview]
Message-ID: <20040616010104.GA23727@penguin2.jf.intel.com> (raw)
In-Reply-To: <40CF9382.2010008@linux.jf.intel.com>
> Andrew Morton wrote:
> >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.
> >>
> >>
> >
> >I expect this functionality can be provided without kernel changes via
> >auditing of the relevant system calls. See
> >http://people.redhat.com/faith/audit/.
If a process segfaults is there currently a message sent from the auditing
code?
> >Maybe there are shortcomings in the current auditing/filtering framework.
> >If so, perhaps they could be addressed.
I have worries about both the complexity required from the client for just
monitoring the life time of a process/thread, and the overhead of doing
this with the auditing/netlink implementation, but do not have any proof.
We can take a crack at implementing a couple of hello world monitors for
process/thread creation and exec'ing, and come back with any limitations
in the existing auditing code that would make this particular type of
monitoring painful.
--rustyl
next prev parent reply other threads:[~2004-06-16 1:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 18:38 [Announce] Non Invasive Kernel Monitor for threads/processes 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 [this message]
2004-06-16 0:39 ` Chris Wright
2004-06-16 12:32 ` Karim Yaghmour
-- strict thread matches above, loose matches on Subject: below --
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=20040616010104.GA23727@penguin2.jf.intel.com \
--to=rusty@linux.jf.intel.com \
--cc=atul_sabharwal@linux.jf.intel.com \
--cc=faith@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.