linux-kernel - Re: [PATCH] implement-system-call-mini-HOWTO.txt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1163405053.15249.104.camel@laptopd505.fenrus.org>
Date:	Mon, 13 Nov 2006 09:04:13 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Amit Choudhary <amit2030@...il.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] implement-system-call-mini-HOWTO.txt

On Sun, 2006-11-12 at 22:14 -0800, Amit Choudhary wrote:
> Description: A mini HOWTO on implementing a new system call. 

> Although, I think that implementing new system calls is discouraged, many people do end up in implementing proprietary system calls. 



what do you mean by that? Do you mean open source-but-forked ? Yes that
is bad, because applications written to use that system call will not
work later on when the upstream kernel uses your system call number for
something else....



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/