From: Matt Helsley <matthltc@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
Jean-Pierre Dion <jean-pierre.dion@bull.net>,
Jesse Barnes <jbarnes@engr.sgi.com>,
Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
Badari Pulavarty <pbadari@us.ibm.com>,
Ram Pai <linuxram@us.ibm.com>,
CKRM-Tech <ckrm-tech@lists.sourceforge.net>,
Erich Focht <efocht@hpce.nec.com>,
elsa-devel <elsa-devel@lists.sourceforge.net>,
Gerrit Huizenga <gh@us.ibm.com>, Adrian Bunk <bunk@stusta.de>,
"Chandra S. Seetharaman" <sekharan@us.ibm.com>
Subject: [PATCH 00/02] Process Events Connector
Date: Tue, 25 Oct 2005 17:07:40 -0700 [thread overview]
Message-ID: <1130285260.10680.194.camel@stark> (raw)
Andrew, all,
Is there any reason this patch could not go for a spin in a -mm tree?
It's similar to Guillaume's fork connector patch which did appear in -mm
at one point. It replaces the fork_advisor patch that ELSA is currently
using, can be used by userspace CKRM code, and in general is useful for
anything that may wish to monitor changes in all processes.
I've modified the patch to future-proof it against proposed interfaces
that call module functions from fork, exit, exec, and set[ug]id paths.
This means that it should be safe to merge without or prior to merging
of those interfaces.
The patches are:
1. Export Connector Symbol - a small patch to export a useful connector
symbol. This enables the following patch.
2. Process Events Connector - This adds connector calls in the fork,
exec, etc. paths and provides a means for userspace to listen for the
generated events.
Thanks,
-Matt Helsley
< matthltc @ us.ibm.com >
next reply other threads:[~2005-10-26 0:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 0:07 Matt Helsley [this message]
2005-10-26 0:09 ` [PATCH 00/02] Process Events Connector Matt Helsley
2005-10-26 0:12 ` [PATCH 02/02] " Matt Helsley
2005-10-26 19:30 ` Andrew Morton
2005-10-26 23:06 ` Matt Helsley
2005-10-26 0:16 ` [PATCH 01/02] Export Connector Symbol Matt Helsley
2005-10-26 6:57 ` Evgeniy Polyakov
2005-10-26 0:34 ` [PATCH 00/02] Process Events Connector Greg KH
2005-10-26 1:00 ` Matt Helsley
2005-10-26 1:16 ` Chandra Seetharaman
2005-10-26 1:22 ` Chris Wright
2005-10-26 1:30 ` [ckrm-tech] " Matt Helsley
2005-10-26 1:48 ` Chris Wright
2005-10-26 2:13 ` Matt Helsley
2005-10-26 18:34 ` Jay Lan
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=1130285260.10680.194.camel@stark \
--to=matthltc@us.ibm.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=efocht@hpce.nec.com \
--cc=elsa-devel@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=guillaume.thouvenin@bull.net \
--cc=jbarnes@engr.sgi.com \
--cc=jean-pierre.dion@bull.net \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=pbadari@us.ibm.com \
--cc=sekharan@us.ibm.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