Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932507AbVJZAfL (ORCPT ); Tue, 25 Oct 2005 20:35:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932505AbVJZAfL (ORCPT ); Tue, 25 Oct 2005 20:35:11 -0400 Received: from mail.kroah.org ([69.55.234.183]:42171 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S932507AbVJZAfJ (ORCPT ); Tue, 25 Oct 2005 20:35:09 -0400 Date: Tue, 25 Oct 2005 17:34:30 -0700 From: Greg KH To: Matt Helsley Cc: Andrew Morton , LKML , Evgeniy Polyakov , Jean-Pierre Dion , Jesse Barnes , Guillaume Thouvenin , Badari Pulavarty , Ram Pai , CKRM-Tech , Erich Focht , elsa-devel , Gerrit Huizenga , Adrian Bunk , "Chandra S. Seetharaman" Subject: Re: [PATCH 00/02] Process Events Connector Message-ID: <20051026003430.GA27680@kroah.com> References: <1130285260.10680.194.camel@stark> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1130285260.10680.194.camel@stark> User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 864 Lines: 21 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 - 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/