linux-kernel - Re: [PATCH 2.6.20-rc5 4/4] sys_futex64 : allows 64bit futexes

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

Date:	Thu, 18 Jan 2007 22:35:50 +0000
From:	Christoph Hellwig <hch@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Pierre Peiffer <pierre.peiffer@...l.net>,
	LKML <linux-kernel@...r.kernel.org>,
	Ulrich Drepper <drepper@...hat.com>,
	Jakub Jelinek <jakub@...hat.com>,
	Jean-Pierre Dion <jean-pierre.dion@...l.net>
Subject: Re: [PATCH 2.6.20-rc5 4/4] sys_futex64 : allows 64bit futexes

On Thu, Jan 18, 2007 at 08:45:56AM +0100, Ingo Molnar wrote:
> actually, we have a big multiplexer there already, so it's only 
> symmetric. Nothing is served by doing it half-assed. I raised the issue 
> of the multiplexer back when the first futex API was merged (years ago), 
> and it was rejected. Now whether you like it or not we've got to live 
> with that decision. You are certainly free to introduce a patchset with 
> a completely new set of syscall vectors to demultiplex all futex APIs, 
> but to just start a half-done demultiplexing makes zero sense.

dding new syscalls for the old functionality is totally pointless as
we have to support the old entry point forever anyway.  And new code
is using the new entry point, so let's get that right.
-
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/