From: Alejandro Colomar <alx@kernel.org>
To: Phosit <phosit@autistici.org>
Cc: linux-man@vger.kernel.org
Subject: Re: Wrong protocol in IPV6_V6ONLY.2const
Date: Sun, 21 Jun 2026 19:17:19 +0200 [thread overview]
Message-ID: <ajgcZCDV116tauEn@devuan> (raw)
In-Reply-To: <b096c7e29014c6aaf416ce672684aab569aac341.camel@autistici.org>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
Hi!
On 2026-06-21T18:00:20+0200, Phosit wrote:
> In the synopsis of "IPV6_V6ONLY.2const" the function signature uses
> `IPPROTO_IP`. When using that the function seems to have no effect. I
> think it should state `IPPROTO_IPV6`.
Thanks! It seems a mistake introduced recently. I've fixed it with
this commit:
commit 3b2ac90b3518635966754ff83d703c5f6029ae74
Author: Alejandro Colomar <alx@kernel.org>
Date: 2026-06-21 19:15:20 +0200
man/man2const/IPV6_V6ONLY.2const: $2 is IPPROTO_IPV6, not IPPROTO_IP
Fixes: 07d5d5b62a8f (2025-12-02; "man/man2const/{IPPROTO_IPV6,IPV6_V6ONLY}.2const: Split IPV6_V6ONLY from IPPROTO_IPV6(2const)")
Reported-by: Phosit <phosit@autistici.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
diff --git a/man/man2const/IPV6_V6ONLY.2const b/man/man2const/IPV6_V6ONLY.2const
index bf8c9aeed560..4ade0db33371 100644
--- a/man/man2const/IPV6_V6ONLY.2const
+++ b/man/man2const/IPV6_V6ONLY.2const
@@ -15,7 +15,7 @@ .SH SYNOPSIS
.BR "#include <netinet/in.h>" " /* Definition of " IP* " constants */"
.B #include <sys/socket.h>
.P
-.BI int\~setsockopt(int\~ sockfd ,\~IPPROTO_IP,\~IPV6_V6ONLY,
+.BI int\~setsockopt(int\~ sockfd ,\~IPPROTO_IPV6,\~IPV6_V6ONLY,
.BI " const\~int\~*" enable ,\~sizeof(int));
.fi
.SH DESCRIPTION
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-06-21 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-21 16:00 Wrong protocol in IPV6_V6ONLY.2const Phosit
2026-06-21 17:17 ` Alejandro Colomar [this message]
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=ajgcZCDV116tauEn@devuan \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=phosit@autistici.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.