[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070607124505.2d829b9b.dada1@cosmosbay.com>
Date: Thu, 7 Jun 2007 12:45:05 +0200
From: Eric Dumazet <dada1@...mosbay.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Davide Libenzi <davidel@...ilserver.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ulrich Drepper <drepper@...hat.com>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: [patch 7/8] fdmap v2 - implement sys_socket2
On Thu, 7 Jun 2007 11:06:23 +0100
Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > I don't think it's a matter of versioning. Many userspace libraries
> > expects their fds to be compact (for many reasons - they use select, they
> > use them to index 0-based arrays, etc...), and if the kernel suddendly
> > starts returning values in the 1<<28 up arena, they sure won't be happy.
> > So I believe that the correct way is that the caller specifically selects
> > the feature, leaving the legacy fd allocation as default.
>
> I don't understand the connection between this paragraph (with which I
> agree) and the urge to add a ton of ugly syscall hacks. "Caller
> specifically selects feature" - > prctl(). Libraries get unhappy ->
> linker issue.
>
Alan, prctl() things are usually inherited at fork()/exec() time.
If you fork() from a new application , then exec an old one
(eventually a statically linked program), we have a problem ?
-
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