From: "David Schwartz" <davids@webmaster.com>
To: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: RE: Problem with unix sockets: SOCK_DGRAM ignores MSG_TRUNC
Date: Tue, 6 Feb 2007 12:11:31 -0800 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKCEKJBGAC.davids@webmaster.com> (raw)
In-Reply-To: <200702061355.39660.daniel.kabs@mobotix.com>
> 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
next prev parent reply other threads:[~2007-02-06 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 11:59 Daniel Kabs
2007-02-05 0:52 ` David Miller
2007-02-06 12:55 ` Daniel Kabs
2007-02-06 20:11 ` David Schwartz [this message]
2007-02-07 8:58 ` Daniel Kabs
2007-02-07 9:31 ` Daniel Kabs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MDEHLPKNGKAHNMBLJOLKCEKJBGAC.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®