[Top] [All Lists]

Re: kernel bug in socketpair()

To: Glenn Fowler <gsf@xxxxxxxxxxxxxxxx>
Subject: Re: kernel bug in socketpair()
From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Date: 23 Jul 2003 20:08:21 +0100
Cc: davem@xxxxxxxxxx, dgk@xxxxxxxxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx
In-reply-to: <200307231854.OAA90112@xxxxxxxxxxxxxxxxxxxxxxx>
References: <200307231428.KAA15254@xxxxxxxxxxxxxxxxxxxxxxx> <20030723074615.25eea776.davem@xxxxxxxxxx> <200307231656.MAA69129@xxxxxxxxxxxxxxxxxxxxxxx> <20030723100043.18d5b025.davem@xxxxxxxxxx> <200307231724.NAA90957@xxxxxxxxxxxxxxxxxxxxxxx> <20030723103135.3eac4cd2.davem@xxxxxxxxxx> <200307231814.OAA74344@xxxxxxxxxxxxxxxxxxxxxxx> <20030723112307.5b8ae55c.davem@xxxxxxxxxx> <200307231854.OAA90112@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Mer, 2003-07-23 at 19:54, Glenn Fowler wrote:
> named unix sockets reside in the fs namespace, no?
> so they must be linked to a dir before use and unlinked after use
> the unlink after use would be particularly tricky for the parent process
> implementing
>       cmd <(cmd ...) ...

Portable stuff yes, Linux also supports a pure socket namespace for them
when the path starts with a nul character

<Prev in Thread] Current Thread [Next in Thread>