From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
Chris Wright <chrisw@osdl.org>,
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>
Subject: Re: [PATCH 00/02] Process Events Connector
Date: Tue, 25 Oct 2005 18:16:48 -0700 [thread overview]
Message-ID: <1130289408.3586.157.camel@linuxchandra> (raw)
In-Reply-To: <1130288437.10680.236.camel@stark>
On Tue, 2005-10-25 at 18:00 -0700, Matt Helsley wrote:
> On Tue, 2005-10-25 at 17:34 -0700, Greg KH wrote:
> > On Tue, Oct 25, 2005 at 05:07:40PM -0700, Matt Helsley wrote:
> > > 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.
> >
> > Why can't you use a lsm module for this instead? It looks like you are
> > wanting to hook things in pretty much the same places we currently have
> > the lsm hooks at.
> >
> > thanks,
> >
> > greg k-h
>
> Guillaume apparently tried to use LSM for his fork connector and was
> told "this doesn't belong here":
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0502.2/1000.html
>
When we tried to use LSM mechanisms for getting callbacks for CKRM that
was the same response we got.
We were told that LSM should be used only for security related
functionality and not for getting hooks into those specific kernel
functions.
> This patch does not affect whether or not these operations succeed and
> hence is a poor match for LSM even though it hooks into the same places
> in the kernel.
>
> There has been some discussion on lse-tech about 'task_notifiers' that
> would allow multiple modules to hook into these paths without polluting
> the paths themselves. I modified the patch with these proposals in mind.
> Then, assuming such an interface developed, I could submit a small patch
> which would convert to using the new interface.
>
> Would you still rather see the patch as an LSM module?
>
> Thanks,
> -Matt Helsley
> < matthltc @ us.ibm.com >
>
>
--
----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@us.ibm.com | .......you may get it.
----------------------------------------------------------------------
next prev parent reply other threads:[~2005-10-26 1:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 0:07 [PATCH 00/02] Process Events Connector Matt Helsley
2005-10-26 0:09 ` 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 [this message]
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=1130289408.3586.157.camel@linuxchandra \
--to=sekharan@us.ibm.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=chrisw@osdl.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=efocht@hpce.nec.com \
--cc=elsa-devel@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=greg@kroah.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=matthltc@us.ibm.com \
--cc=pbadari@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