linux-kernel - Re: Idea: Feature information / extensions dispatcher syscall.

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: <20090422161257.2743ea33@lxorguk.ukuu.org.uk>
Date:	Wed, 22 Apr 2009 16:12:57 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Igor Zhbanov <izh1979@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Idea: Feature information / extensions dispatcher syscall.

> But in some cases syscalls are more convenient than reading/writing/ioctling
> in /proc, /sys or /dev.

A syscall and an ioctl are the same thing except that you need a file
handle for one of them.

> And I suggest to regulate syscalls usage and reserve a set of numbers
> "home" modules used in some organizations only.

We have file system naming so you can open device or sysfs and the like
files to do that job. That avoids the problem of trying to keep numbering
sane.

Alan

--
	"Alan, I'm getting a bit worried about you."
				-- Linus Torvalds
--
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/