[Top] [All Lists]

Re: kernel bug in socketpair()

To: "David S. Miller" <davem@xxxxxxxxxx>
Subject: Re: kernel bug in socketpair()
From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Date: 23 Jul 2003 17:13:40 +0100
Cc: dgk@xxxxxxxxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, gsf@xxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20030723083621.26429e51.davem@xxxxxxxxxx>
References: <200307231332.JAA26197@xxxxxxxxxxxxxxxxxxxxxxx> <1058970007.5520.68.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20030723083621.26429e51.davem@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Mer, 2003-07-23 at 16:36, David S. Miller wrote:
> > This is intentional - sockets do not have an "open" operation currently.
> Sure, but we've known this for a long time.
> And because we knew, we decided not to add an "open"
> method to sockets.  The reason, as I remember it, was
> security.
> Was it not?

Mostly if I remember rightly that if you don't do the check because you have
no open operation to create a new instance you crash the box. HPA did have 
some sensible ideas about how to do "open" on AF_UNIX sockets but for the 
others its really unclear quite what "open" means

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