From: Vladislav Ivanishin <vlad@ispras.ru>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: [patch] recv.2: Mention SOCK_SEQPACKET in MSG_TRUNC flag description
Date: Sun, 27 Nov 2022 13:38:13 +0300 [thread overview]
Message-ID: <87v8n03coa.fsf@ispras.ru> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: 0001-recv.2-Mention-SOCK_SEQPACKET-in-MSG_TRUNC-descripti.patch --]
[-- Type: text/x-patch, Size: 917 bytes --]
unix_seqpacket_recvmsg() calls unix_dgram_recvmsg() which handles
MSG_TRUNC. This has been the case since the support for this flag was
implemented in the latter; the sequential-packet socket type seems to
have been left out from the description by an oversight.
Signed-off-by: Vladislav Ivanishin <vlad@ispras.ru>
---
man2/recv.2 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/man2/recv.2 b/man2/recv.2
index d492976c4..c5f1a9d70 100644
--- a/man2/recv.2
+++ b/man2/recv.2
@@ -226,7 +226,8 @@ subsequent receive call will return the same data.
For raw
.RB ( AF_PACKET ),
Internet datagram (since Linux 2.4.27/2.6.8),
-netlink (since Linux 2.6.22), and UNIX datagram
+netlink (since Linux 2.6.22),
+and UNIX datagram as well as sequenced-packet
.\" commit 9f6f9af7694ede6314bed281eec74d588ba9474f
(since Linux 3.4) sockets:
return the real length of the packet or datagram,
--
2.37.3
next reply other threads:[~2022-11-27 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 10:38 Vladislav Ivanishin [this message]
2022-12-11 16:09 ` [patch] recv.2: Mention SOCK_SEQPACKET in MSG_TRUNC flag description Alejandro Colomar
2023-02-12 13:38 ` Vladislav Ivanishin
2023-02-12 19:14 ` Alejandro Colomar
2023-02-13 5:38 ` Vladislav Ivanishin
2023-02-20 5:37 ` Vladislav Ivanishin
2023-03-05 18:06 ` Vladislav Ivanishin
2023-03-05 18:33 ` Alejandro Colomar
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=87v8n03coa.fsf@ispras.ru \
--to=vlad@ispras.ru \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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