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]

Message-ID: <Pine.LNX.4.64.0706092033220.23139@alien.or.mcafeemobile.com>
Date:	Sat, 9 Jun 2007 20:35:55 -0700 (PDT)
From:	Davide Libenzi <davidel@...ilserver.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	Al Viro <viro@....linux.org.uk>,
	Kyle Moffett <mrmacman_g4@....com>,
	Ulrich Drepper <drepper@...hat.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Theodore Tso <tytso@....edu>,
	Eric Dumazet <dada1@...mosbay.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [patch 7/8] fdmap v2 - implement sys_socket2

On Sat, 9 Jun 2007, Linus Torvalds wrote:

> On Sat, 9 Jun 2007, Al Viro wrote:
> > 
> > Eww...  Idea of pipe(2) taking flags as argument...
> 
> Right. That was one of the patches, and it was one that I said was too 
> damn ugly to live.
> 
> So I instead suggested the alternate approach of adding a single new 
> system call that runs another system call indirectly, with a set of flags 
> and/or other behaviour modifications.

What if we put a data section in the vdso and we let userspace set the 
flags or whatever in there? Syslets could use one of those bits to set the 
"threadlet mode" w/out calling a syscall at all.
In that way we have no new syscalls whatsoever. No?


- Davide


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