[Bug manual/28299] New: Network namespace argument specified to be AF_LOCAL

[Bug manual/28299] New: Network namespace argument specified to be AF_LOCAL

[izhangyuxing at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=28299

            Bug ID: 28299
           Summary: Network namespace argument specified to be AF_LOCAL
           Product: glibc
           Version: 2.34
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: manual
          Assignee: unassigned at sourceware dot org
          Reporter: izhangyuxing at gmail dot com
                CC: mtk.manpages at gmail dot com
  Target Milestone: ---

In chapter 16.8.3 Socket Pairs, in the paragraph describing function
socketpair, it is stated that the argument namespace must be AF_LOCAL. However,
AF_LOCAL is the address family of the corresponding namespace PF_LOCAL, which
should have been specified instead.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug manual/28299] Network namespace argument specified to be AF_LOCAL

[mtk.manpages at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=28299

--- Comment #1 from Michael Kerrisk <mtk.manpages at gmail dot com> ---
(In reply to Yuxing Zhang from comment #0)
> In chapter 16.8.3 Socket Pairs, in the paragraph describing function
> socketpair, it is stated that the argument namespace must be AF_LOCAL.
> However, AF_LOCAL is the address family of the corresponding namespace
> PF_LOCAL, which should have been specified instead.

This is questionable. In the original conception, it was intended that there
might be a one-to-many relationship between PF_* and AF_*. But, in practice,
there's always been a one-to-one correspondence between the AF_* and PF_*
constants, as far as I know. POSIX does not even specify the PF_* constants.
Stevens UNPv1 has more to say about this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.