Re: [PATCH] linux 2.9.10-rc1: Fix oops in unix_dgram_sendmsg when using SELinux and SOCK_SEQPACKET

From: Chris Wright (chrisw_at_osdl.org)
Date: 11/18/04

  • Next message: Jan Engelhardt: "Re: [patch 2.6.10-rc2] oss: AC97 quirk facility" 
    Date:	Thu, 18 Nov 2004 10:34:11 -0800
To: Alan Cox <alan@lxorguk.ukuu.org.uk>

    * 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/
  • Next message: Jan Engelhardt: "Re: [patch 2.6.10-rc2] oss: AC97 quirk facility"

    Relevant Pages

    • 2.6.0 - Network doesnt come up.
      ... Bringing up loopback interface: arping: socket: Address family not supported ... some other host already uses address 127.0.0.1. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] linux 2.9.10-rc1: Fix oops in unix_dgram_sendmsg when using SELinux and SOCK_SEQPACKET
      ... > sendto() on a non connected socket should fail with ENOTCONN. ... A network protocol can implement lazy binding ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • HEADS UP: network stack and socket hackery over the next few weeks
      ... Over the next few weeks, I'll be doing a fairly serious workworking of the socket and protocol reference models, in order to clean up a number of long-standing race conditions and provide infrastructure for significant locking optimizations for several protocols (including TCP). ...
      (freebsd-current)
    • Re: socket arguments
      ... a protocol argument of zero means unspecified. ... socket type, protocol) parameters. ... ProviderFlags: MatchesProtoZero ...
      (microsoft.public.win32.programmer.networks)
    • Re: sosend/soreceive consistency improvements
      ... As part of cleanups, locking, and optimization work, I've been looking at ... protocol could provide substitute implementations. ... There's another side to the pluggability, however -- the socket consumers ... New references to sosend() and soreceiveperiodically ...
      (freebsd-arch)