RE: Problem with unix sockets: SOCK_DGRAM ignores MSG_TRUNC

> Why not improve consistency and make unix_dgram_recvmsg() return the full
> packet length? So it would behave as UDP does. What do you think about
> adding the following code to linux/net/unix/af_unix.c:

It would be nice if the world worked that way, but you can't break POSIX
compliance. Perhaps another receive flag?

DS


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Problem with unix sockets: SOCK_DGRAM ignores MSG_TRUNC
    • From: Daniel Kabs <[email protected]>

• References:
  • Re: Problem with unix sockets: SOCK_DGRAM ignores MSG_TRUNC
    • From: Daniel Kabs <[email protected]>

• Prev by Date: Re: +1 4 cz (Re: [Ksummit-2006-discuss] 2007 Linux Kernel Summit)
• Next by Date: Re: cpu load balancing problem on smp
• Previous by thread: Re: Problem with unix sockets: SOCK_DGRAM ignores MSG_TRUNC
• Next by thread: Re: Problem with unix sockets: SOCK_DGRAM ignores MSG_TRUNC
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]