[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0706091508480.14445@alien.or.mcafeemobile.com>
Date: Sat, 9 Jun 2007 15:12:54 -0700 (PDT)
From: Davide Libenzi <davidel@...ilserver.org>
To: Matt Mackall <mpm@...enic.com>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
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, 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists