All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaya Potter <spotter@yucs.org>
To: linux-kernel@vger.kernel.org
Subject: process creation/deletions hooks
Date: 27 Mar 2003 16:08:10 -0500	[thread overview]
Message-ID: <1048799290.31010.62.camel@zaphod> (raw)

We are trying to write a module that does it's own accounting of
processes as they are created and deleted.  We have an extremely ugly
hack of taking care of process creation (wrap fork() and clone() in a
syscall wrapper, as that's the only way processes can be created).  

However, doing the same for exit() doesn't work, because processes don't
have to call exit() to die, but can be killed any of number of ways, and
go straight to the do_exit() code.

I would imagine one would hook a void * function that takes some sort of
defined argument, perhaps a pointer to the task_struct (as it will be
called in do_exit, it would seem locking shouldn't be an issue) and what
the function is allowed to do would be defined.

Would people be for/against an interface that allows for modules to
register functions that can be called on process creation/deletion.  It
would help us avoid the hacks, such as I described, and I imagine could
have benefit others.

thanks,

shaya


             reply	other threads:[~2003-03-27 20:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27 21:08 Shaya Potter [this message]
2003-03-27 21:31 ` process creation/deletions hooks Nathan Straz
2003-03-27 23:56   ` Shaya Potter
2003-03-28  1:03     ` Shaya Potter
2003-03-28  2:35       ` Robert White
2003-03-29  2:03 ` Chris Wright
2003-03-30  1:50   ` Shaya Potter
2003-03-30  1:52     ` Chris Wright
2003-03-30  2:01       ` Shaya Potter
2003-03-30  3:13         ` Chris Wright

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=1048799290.31010.62.camel@zaphod \
    --to=spotter@yucs.org \
    --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.