linux-kernel - Re: [PATCH 0/2] man7/ip.7: Clarify PKTINFO's docs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b89c3f75-0b70-4620-b525-b264adb74c7b@dzwdz.net>
Date: Tue, 25 Nov 2025 02:50:19 +0100
From: dzwdz <not@...dz.net>
To: Alejandro Colomar <alx@...nel.org>
Cc: linux-man@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
 Linux API <linux-api@...r.kernel.org>, ej@...i.de
Subject: Re: [PATCH 0/2] man7/ip.7: Clarify PKTINFO's docs

On 11/18/25 14:51, Alejandro Colomar wrote:
> Do you suggest moving each socket option to a manual page under
> man2const/?  I think I agree with that.  There's precedent, and it makes
> the pages more readable.

In general - yes, definitely!

However, struct in_pktinfo can be passed to sendmsg even if IP_PKTINFO 
isn't set, so I don't think it would make sense to document it in e.g. 
IP_PKTINFO(2const) - it should probably get its own manpage in man2type.
That option, in turn, only makes sense in the context of that struct, so 
I think it should probably be documented in in_pktinfo(2type).

This would /kinda/ be like how e.g. PA_INT(3const) points to 
printf.h(3head), I guess?

I'd be happy to try writing that manpage if you think this approach 
makes sense :)

Thanks,
dzwdz

Download attachment "OpenPGP_signature.asc" of type "application/pgp-signature" (237 bytes)