From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 104561] New: Autobind in unix domain sockets always requires call to bind
Date: Tue, 15 Sep 2015 07:45:12 +0000 [thread overview]
Message-ID: <bug-104561-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=104561
Bug ID: 104561
Summary: Autobind in unix domain sockets always requires call
to bind
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
Reporter: a0vhv-zqRNUXuvxA0b1SvskN2V4Q@public.gmane.org
Regression: No
Created attachment 187571
--> https://bugzilla.kernel.org/attachment.cgi?id=187571&action=edit
Example code that shows bind() is necessary for autobind
In "man 7 unix" it says:
"If a bind(2) call specifies addrlen as sizeof(sa_family_t), or the SO_PASSCRED
socket option was specified for a socket that was not explicitly bound to an
address, then the socket is autobound to an abstract address."
However, only setting SO_PASSCRED is not enough to autobind. You always have to
call bind, as you can see in the attached example. If you run it, every call
should succeed and getsockname reports that the autobind address has a size of
8 bytes.
Now remove lines 20-22, so the socket gets no longer explicitly bound.
getsockname reports that the address size is 2 bytes (because
bound_addr.sun_path is not used) and the call to "listen" fails.
So it seems the call to "bind" is necessary even if SO_PASSCRED is used.
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2015-09-15 7:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-104561-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).