Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761940AbXFIWNK (ORCPT ); Sat, 9 Jun 2007 18:13:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760632AbXFIWM5 (ORCPT ); Sat, 9 Jun 2007 18:12:57 -0400 Received: from x35.xmailserver.org ([64.71.152.41]:1166 "EHLO x35.xmailserver.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756277AbXFIWM4 (ORCPT ); Sat, 9 Jun 2007 18:12:56 -0400 X-AuthUser: davidel@xmailserver.org Date: Sat, 9 Jun 2007 15:12:54 -0700 (PDT) From: Davide Libenzi X-X-Sender: davide@alien.or.mcafeemobile.com To: Matt Mackall cc: Linus Torvalds , Al Viro , Kyle Moffett , Ulrich Drepper , Alan Cox , Theodore Tso , Eric Dumazet , Linux Kernel Mailing List , Andrew Morton , Ingo Molnar Subject: Re: [patch 7/8] fdmap v2 - implement sys_socket2 In-Reply-To: <20070609214120.GD11166@waste.org> Message-ID: References: <466A0BFB.3070908@redhat.com> <20070609151521.GD4095@ftp.linux.org.uk> <466AD4BA.80407@redhat.com> <20070609165454.GE4095@ftp.linux.org.uk> <466ADEAB.7080202@redhat.com> <20070609172429.GF4095@ftp.linux.org.uk> <2E51520E-EC73-457F-809A-4749ED9A3C97@mac.com> <20070609200645.GG4095@ftp.linux.org.uk> <20070609214120.GD11166@waste.org> X-GPG-FINGRPRINT: CFAE 5BEE FD36 F65E E640 56FE 0974 BF23 270F 474E X-GPG-PUBLIC_KEY: http://www.xmailserver.org/davidel.asc MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1157 Lines: 34 On Sat, 9 Jun 2007, Matt Mackall wrote: > On Sat, Jun 09, 2007 at 01:31:56PM -0700, Davide Libenzi wrote: > > On Sat, 9 Jun 2007, Linus Torvalds wrote: > > > > > So I think both the FD_CLOEXEC _and_ the "private fd space" are real > > > issues. I don't agree with the "random fd" approach. I'd much rather have > > > a non-random setup for the nonlinear ones (it just shouldn't be linear). > > > > That is fine for me. So what about the randomness? > > > > A) Don't do it at all > > > > B) Let userspace select it in some way globally > > > > C) Let userspace select it per-fd (this won't be an O(1) anymore though) > > It should be handled the same way that VMA layout randomness is > handled. There are multiple knobs including ELF markers and /proc > bits. You mean a global bit controlled by /proc, eventually overridden by an ELF flag? An maybe a prctl() to give sw configurability? - Davide - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/