Subject: Re: Two fixes for 2.4.19-pre5-ac3
To: mulix@actcom.co.il (Muli Ben-Yehuda)
Date: Sun, 7 Apr 2002 21:29:01 +0100 (BST)
Cc: movement@marcelothewonderpenguin.com (John Levon),
        alan@lxorguk.ukuu.org.uk (Alan Cox),
        shirsch@adelphia.net (Steven N. Hirsch), linux-kernel@vger.kernel.org
In-Reply-To: <20020407225504.Z10733@actcom.co.il> from "Muli Ben-Yehuda" at Apr 07, 2002 10:55:04 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E16uJHZ-0006eO-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Sender: linux-kernel-owner@vger.kernel.org

> hijacks syscall entries in the sys_call_table as well, because we
> want it to work as a module and not require patching the kernel. Our
> solution to the module unload race on syscall de-hijacking is simple,
> splitting the system call hijacking code into a single small module
> which once loaded cannot be unloaded.

So your small module can export a function called 
	patch_syscall(NR_foo, function);

Now you can put the arch specific syscall patching code into your small
common module and its cleaner anyway ?

Alan
-
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/