Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932511AbVJZBQw (ORCPT ); Tue, 25 Oct 2005 21:16:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932514AbVJZBQw (ORCPT ); Tue, 25 Oct 2005 21:16:52 -0400 Received: from e31.co.us.ibm.com ([32.97.110.149]:999 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id S932511AbVJZBQv (ORCPT ); Tue, 25 Oct 2005 21:16:51 -0400 Subject: Re: [PATCH 00/02] Process Events Connector From: Chandra Seetharaman Reply-To: sekharan@us.ibm.com To: Matt Helsley Cc: Greg KH , Andrew Morton , Chris Wright , LKML , Evgeniy Polyakov , Jean-Pierre Dion , Jesse Barnes , Guillaume Thouvenin , Badari Pulavarty , Ram Pai , CKRM-Tech , Erich Focht , elsa-devel , Gerrit Huizenga , Adrian Bunk In-Reply-To: <1130288437.10680.236.camel@stark> References: <1130285260.10680.194.camel@stark> <20051026003430.GA27680@kroah.com> <1130288437.10680.236.camel@stark> Content-Type: text/plain Organization: IBM Date: Tue, 25 Oct 2005 18:16:48 -0700 Message-Id: <1130289408.3586.157.camel@linuxchandra> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-6) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2392 Lines: 62 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. ---------------------------------------------------------------------- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/