linux-kernel - Re: [patch 7/8] fdmap v2

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]

Date:	Fri, 8 Jun 2007 20:48:36 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Davide Libenzi <davidel@...ilserver.org>
Cc:	Ulrich Drepper <drepper@...hat.com>, Theodore Tso <tytso@....edu>,
	Eric Dumazet <dada1@...mosbay.com>,
	Kyle Moffett <mrmacman_g4@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [patch 7/8] fdmap v2 - implement sys_socket2

> So, what do you plan to do? Those handle won't be zero-based. Your 
> "working" system I immagine will do:
> 
> 	bleeh[handle - BASE].duh = ...;
> 
> How nice for a working system. If you *store* the handle returned by the 
> OS, and you *use* the handle to call for OS services, you will be fine 
> independently from the value handed out by the OS.

Well there are two ways I'd do this

#1: Throw the whole thing away and accept its not a good idea anyway

#2: If I was really going this way and I wanted to use it for serious
tricks for high performance I/O then I'd provide the handle from
userspace so that the strategy for allocation is controlled by the caller
who is the only one who can make the smart decisions
-
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/