[Top] [All Lists]

Re: kernel bug in socketpair()

To: davem@xxxxxxxxxx, gsf@xxxxxxxxxxxxxxxx
Subject: Re: kernel bug in socketpair()
From: Glenn Fowler <gsf@xxxxxxxxxxxxxxxx>
Date: Wed, 23 Jul 2003 15:11:47 -0400 (EDT)
Cc: dgk@xxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
Organization: AT&T Labs Research
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> <20030723120457.206dc02d.davem@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Wed, 23 Jul 2003 12:04:57 -0700 David S. Miller wrote:
> Is bash totally broken because of all this?  Or does the problem only
> trigger when using (cmd) subprocesses in a certain way?

bash uses pipe() so its ok
using socketpair() instead of pipe() introduces the problem
and we will now have to find an alternative to work around the
linux /dev/fd/N implementation


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