From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 39652] connect (2) under IPv6 has an incomplete list of returnable error numbers
Date: Wed, 25 Jun 2014 20:03:16 +0000 [thread overview]
Message-ID: <bug-39652-11311-oaQNcZSoe2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-39652-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=39652
--- Comment #2 from Tim Chappell <kernel-3dJX9IkHV5SkwWA8rprFa0EOCMrvLtNR@public.gmane.org> ---
Nick,
Thanks for the reply. I've just tested this with version 3.53 of the man pages
and it now seems correct, apart from:
1. EHOSTUNREACH - this is still missing as a potential reason. I believe it
should be added and the causes are ICMPv6 type 1 code 3 (Address unreachable -
I've verified this to be the case) or ICMPv6 type 3 (Time exceeded – I haven't
verified this case - please check source code).
2. There's also no mention of:
EMSGSIZE or EPROTO - did you check these? I haven't rechecked the source since
I originally raised the issue.
Best wishes,
Tim.
--
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
prev parent reply other threads:[~2014-06-25 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 17:55 [Bug 39652] New: connect (2) under IPv6 has an incomplete list of returnable error numbers bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
[not found] ` <bug-39652-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2014-06-25 16:02 ` [Bug 39652] " bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2014-06-25 20:03 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [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=bug-39652-11311-oaQNcZSoe2@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 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.