Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262095AbVDRPGU (ORCPT ); Mon, 18 Apr 2005 11:06:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262096AbVDRPGU (ORCPT ); Mon, 18 Apr 2005 11:06:20 -0400 Received: from zproxy.gmail.com ([64.233.162.205]:6528 "EHLO zproxy.gmail.com") by vger.kernel.org with ESMTP id S262095AbVDRPGM convert rfc822-to-8bit (ORCPT ); Mon, 18 Apr 2005 11:06:12 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Bsbv5zeody9XKMxyTuQywV4C/3HOVL+Rxv/MjJQ67IWtmH58faHWccoBR6AwGg5gmGoQhTqV0ItmT/SRah4Lvkgs4/e4ylpyghVm6yGtNmzb9DpkW7+aHKUk7AxPdl4AfgELSx9yvarKdq6NGrM7Dlo+FFPkWAaaf3tU5v+RSNQ= Message-ID: <6533c1c9050418080639e41fb@mail.gmail.com> Date: Mon, 18 Apr 2005 11:06:11 -0400 From: Igor Shmukler Reply-To: Igor Shmukler To: Arjan van de Ven Subject: Re: intercepting syscalls Cc: Rik van Riel , Daniel Souza , linux-kernel@vger.kernel.org In-Reply-To: <1113836378.6274.69.camel@laptopd505.fenrus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Content-Disposition: inline References: <6533c1c905041511041b846967@mail.gmail.com> <1113588694.6694.75.camel@laptopd505.fenrus.org> <6533c1c905041512411ec2a8db@mail.gmail.com> <6533c1c905041512594bb7abb4@mail.gmail.com> <6533c1c905041807487a872025@mail.gmail.com> <1113836378.6274.69.camel@laptopd505.fenrus.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1005 Lines: 23 > > Intercepting system call table is an elegant way to solve many > > problems. > > I think I want to take offence to this. It's the worst possible way to > solve many problems, especially since almost everyone who did this to > get anything done until today got it wrong. > > It's about locking. Portability. Stability > > but also about doing things at the right layer. The syscall layer is > almost NEVER the right layer. > > Can you explain exactly what you are trying to do (it's not a secret I > assume, kernel modules are GPL and open source after all, esp such > invasive ones) and I'll try to tell you why it's wrong to do it at the > syscall intercept layer... deal ? now, when I need someone to tell I do something wrong, I know where to go :) - 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/