From: Matthew House <mattlloydhouse@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: [PATCH v2] recv.2: Document MSG_CMSG_CLOEXEC as returned in msg_flags
Date: Sun, 16 Jul 2023 19:47:53 -0400 [thread overview]
Message-ID: <20230716234803.851580-1-mattlloydhouse@gmail.com> (raw)
In-Reply-To: <363c0f82-969d-1927-1bd5-b664cfc83a87@kernel.org>
Signed-off-by: Matthew House <mattlloydhouse@gmail.com>
---
Clarified that the argument comes from the recvmsg() call. It feels a bit
redundant to name recvmsg() again here, given that the list of flags is
immediately preceded by, "The msg_flags field in the msghdr is set on
return of recvmsg(). It can contain several flags: [...]" But I'll let you
be the judge of that.
man2/recv.2 | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/man2/recv.2 b/man2/recv.2
index 660c103fb..1cd9f3e1b 100644
--- a/man2/recv.2
+++ b/man2/recv.2
@@ -412,6 +412,15 @@ is returned to indicate that expedited or out-of-band data was received.
.B MSG_ERRQUEUE
indicates that no data was received but an extended error from the socket
error queue.
+.TP
+.BR MSG_CMSG_CLOEXEC " (since Linux 2.6.23)"
+.\" commit 4a19542e5f694cd408a32c3d9dc593ba9366e2d7
+indicates that
+.B MSG_CMSG_CLOEXEC
+was specified in the
+.I flags
+argument of
+.BR recvmsg ().
.SH RETURN VALUE
These calls return the number of bytes received, or \-1
if an error occurred.
--
2.41.0
next prev parent reply other threads:[~2023-07-16 23:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 21:33 [PATCH] recv.2: Document MSG_CMSG_CLOEXEC as returned in msg_flags Matthew House
2023-07-15 15:36 ` Alejandro Colomar
2023-07-16 23:47 ` Matthew House [this message]
2023-07-17 23:10 ` [PATCH v2] " Alejandro Colomar
2023-07-18 6:00 ` Matthew House
2023-07-18 12:03 ` Alejandro Colomar
2023-07-18 17:26 ` [PATCH v3] " Matthew House
2023-07-18 21:39 ` 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=20230716234803.851580-1-mattlloydhouse@gmail.com \
--to=mattlloydhouse@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@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