All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Erik Jacobson <erikj@sgi.com>, Matthew Helsley <matthltc@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, pagg@oss.sgi.com
Subject: Re: [PATCH 1/3] Process Notification / pnotify
Date: Mon, 3 Oct 2005 12:49:18 -0700	[thread overview]
Message-ID: <20051003124918.2a65ef41.pj@sgi.com> (raw)
In-Reply-To: <20051003184644.GA19106@sgi.com>

Hmmm ... I notice with interest two notification patches posted in
the last few days to lkml:

  Matthew Helsley's Process Events Connector (posted 28 Sep 2005)
  Erik Jacobson's pnotify (posted 3 Oct 2005)

I suspect Matthew and Erik will both instantly hate me for asking, but
does it make sense to integrate these two?

If I understand these two proposals correctly:

    Helsley adds hooks in fork, exec, id change, and exit, to pass
    events to userspace.

    Jacobson adds hooks in fork, exec and exit, to pass events to
    kernel routines and loadable modules.

Perhaps, just brainstorming here, it would make sense for Halsley to
register with pnotify instead of adding his own hooks in parallel.
This presumes that pnotify is accepted into the kernel, and that
pnotify adds the id change hook that Helsley requires.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  parent reply	other threads:[~2005-10-03 19:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-03 18:46 [PATCH 1/3] Process Notification / pnotify Erik Jacobson
2005-10-03 18:51 ` [PATCH 2/3] Process Notification / pnotify user: keyrings Erik Jacobson
2005-10-03 19:02   ` [PATCH 3/3] Process Notification / pnotify user: Job Erik Jacobson
2005-10-04 15:34     ` serue
2005-10-04 15:42       ` Erik Jacobson
2005-10-04 16:03       ` Erik Jacobson
2005-10-03 19:49 ` Paul Jackson [this message]
2005-10-03 23:19   ` [PATCH 1/3] Process Notification / pnotify Matt Helsley

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=20051003124918.2a65ef41.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=erikj@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthltc@us.ibm.com \
    --cc=pagg@oss.sgi.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 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.