Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262568AbUJ0Sxx (ORCPT ); Wed, 27 Oct 2004 14:53:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262518AbUJ0Sx1 (ORCPT ); Wed, 27 Oct 2004 14:53:27 -0400 Received: from rwcrmhc11.comcast.net ([204.127.198.35]:64190 "EHLO rwcrmhc11.comcast.net") by vger.kernel.org with ESMTP id S262569AbUJ0SsX (ORCPT ); Wed, 27 Oct 2004 14:48:23 -0400 Message-ID: <417FED6E.3010007@comcast.net> Date: Wed, 27 Oct 2004 14:48:14 -0400 From: John Richard Moser User-Agent: Mozilla Thunderbird 0.8 (X11/20041022) X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Reserving a syscall number X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1183 Lines: 30 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 How would one go about having a specific syscall number reserved in entry.S? I'm exploring doing a kill inside the kernel from a detection done in userspace, which would allow the executable header of the binary to indicate whether the task should be killed or not; if it works, the changes will likely not go into mainline, but will still require a non-changing syscall index (assuming I understood the syscall manpage properly). On a side note, if a syscall doesn't exist, how would that be detected in userspace? - -- All content of all messages exchanged herein are left in the Public Domain, unless otherwise explicitly stated. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBf+1thDd4aOud5P8RAkeNAJsFJD2l7Up62+/P+SHbJ3l7MwbM0gCfUE/Y vDgYr0SXlrkrwXZyEZw86QE= =jmbP -----END PGP SIGNATURE----- - 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/