Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261229AbUKSBqu (ORCPT ); Thu, 18 Nov 2004 20:46:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262861AbUKRSk6 (ORCPT ); Thu, 18 Nov 2004 13:40:58 -0500 Received: from fw.osdl.org ([65.172.181.6]:8376 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S262857AbUKRSeP (ORCPT ); Thu, 18 Nov 2004 13:34:15 -0500 Date: Thu, 18 Nov 2004 10:34:11 -0800 From: Chris Wright To: Alan Cox Cc: James Morris , Ross Kendall Axe , netdev@oss.sgi.com, Stephen Smalley , lkml , Chris Wright , "David S. Miller" Subject: Re: [PATCH] linux 2.9.10-rc1: Fix oops in unix_dgram_sendmsg when using SELinux and SOCK_SEQPACKET Message-ID: <20041118103411.P2357@build.pdx.osdl.net> References: <1100796294.6019.8.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1100796294.6019.8.camel@localhost.localdomain>; from alan@lxorguk.ukuu.org.uk on Thu, Nov 18, 2004 at 04:45:14PM +0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 915 Lines: 24 * Alan Cox (alan@lxorguk.ukuu.org.uk) wrote: > On Iau, 2004-11-18 at 03:42, James Morris wrote: > > > Well, my reading of socket(2) suggests that it's _not_ supposed to work. > > > > sendto() on a non connected socket should fail with ENOTCONN. > > Not entirely true at all. A network protocol can implement lazy binding > and > do implicit binding on the sendto. Other protocols might not actually > have > a receiving component so have no bind() functionality at all. Just to be clear, this fix is not at socket layer, but specific to UNIX domain socket protocol layer. thanks, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net - 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/