linux-kernel - [PATCH 0/6] kill __KERNEL_SYSCALLS_

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-next>] [day] [month] [year] [list]

Message-Id: <20060830124356.567568000@klappe.arndb.de>
Date:	Wed, 30 Aug 2006 14:43:56 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-kernel@...r.kernel.org
Cc:	linux-arch@...r.kernel.org, Jeff Dike <jdike@...toit.com>,
	Bjoern Steinbrink <B.Steinbrink@....de>,
	Arjan van de Ven <arjan@...radead.org>,
	Chase Venters <chase.venters@...entec.com>,
	Andrew Morton <akpm@...l.org>,
	David Howells <dhowells@...hat.com>, Andi Kleen <ak@...e.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: [PATCH 0/6] kill __KERNEL_SYSCALLS__, try #3

This should address all comments I got for the second version.
Since there is no common agreement on what should happen to
the _syscallX macros, I'm not touching them at all this time.

Whoever wants to remove, reenable or replace them, should send
a separate set of patches for these. With my patches, these
macros are not used in the kernel, and not useable from user
space, so we should probably do _something_ about them.

	Arnd <><

--

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