Messages in this thread | | | Subject | Re: kernel bug in socketpair() | From | Alan Cox <> | Date | 23 Jul 2003 15:20:08 +0100 |
| |
On Mer, 2003-07-23 at 14:32, David Korn wrote: > The first problem is that files created with socketpair() are not accessible > via /dev/fd/n or /proc/$$/fd/n where n is the file descriptor returned > by socketpair(). Note that this is not a problem with pipe().
This is intentional - sockets do not have an "open" operation currently.
> The second problem is that if fchmod(fd,S_IWUSR) is applied to the write end > of a pipe(), it causes the read() end to also be write only so that > opening /dev/fd/n for read fails.
That doesn't directly suprise me. Our pipes are BSD style not streams pipes. One thing that means is that the pipe itself is a single inode.
- 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/
| |