From: Pablo Neira Ayuso <pablo-Cap9r6Oaw4JrovVCs/uTlw@public.gmane.org>
To: "Fernando Luis Vázquez Cao"
<fernando_b1-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Cc: Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netfilter-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Patrick McHardy <kaber-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>,
Hirotaka Sasaki
<sasaki.hirotaka-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Subject: Re: [PATCH 2/2] man/send(2): document a long standing bug that can cause spurious EPERM errors
Date: Tue, 19 Mar 2013 11:12:23 +0100 [thread overview]
Message-ID: <20130319101223.GA3672@localhost> (raw)
In-Reply-To: <1363675960.4767.10.camel@nexus>
On Tue, Mar 19, 2013 at 03:52:40PM +0900, Fernando Luis Vázquez Cao wrote:
> Subject: [PATCH 2/2] man/send(2): document a long standing bug that can cause spurious EPERM errors
>
> This bug has been known since early 2009 (the latest) and discussed in
> netdev before:
>
> http://marc.info/?l=linux-netdev&w=2&r=1&s=Possible+race+condition+in+conntracking+&q=b
>
> It seems that a proper fix would be non trivial, so document the bug
> in the meantime.
>
> Reported-by: Hirotaka Sasaki <sasaki.hirotaka-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
> Signed-off-by: Fernando Luis Vazquez Cao <fernando-gVGce1chcLdL9jVzuh4AOg@public.gmane.org>
> ---
>
> diff -urNp man-pages-3.50-orig/man2/send.2 man-pages-3.50/man2/send.2
> --- man-pages-3.50-orig/man2/send.2 2013-03-19 15:18:03.784306647 +0900
> +++ man-pages-3.50/man2/send.2 2013-03-19 15:30:40.788060426 +0900
> @@ -420,6 +420,11 @@ Linux may return
> .B EPIPE
> instead of
> .BR ENOTCONN .
> +
> +Linux may return spurious
> +.B EPERM
> +errors when netfilter's conntrack module is loaded and two or more
> +UDP packets belonging to the same connection are processed in parallel.
The Connection tracking system may drop packets for different reasons
under rare circunstances, not only in this case.
I'd prefer if you only apply patch 1/2.
--
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
next prev parent reply other threads:[~2013-03-19 10:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 6:45 [PATCH 1/2] man/send(2): add EPERM to the list of possible errors Fernando Luis Vázquez Cao
2013-03-19 6:52 ` [PATCH 2/2] man/send(2): document a long standing bug that can cause spurious EPERM errors Fernando Luis Vázquez Cao
2013-03-19 10:12 ` Pablo Neira Ayuso [this message]
2013-03-21 5:07 ` Fernando Luis Vazquez Cao
2013-03-26 8:37 ` [PATCH 1/2] man/send(2): add EPERM to the list of possible errors Fernando Luis Vazquez Cao
2013-03-26 10:48 ` Pablo Neira Ayuso
2013-03-27 4:14 ` Fernando Luis Vazquez Cao
2013-03-27 17:51 ` Pablo Neira Ayuso
2013-03-28 5:37 ` Fernando Luis Vazquez Cao
2013-03-27 17:42 ` Pablo Neira Ayuso
2013-03-28 2:46 ` Fernando Luis Vazquez Cao
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=20130319101223.GA3672@localhost \
--to=pablo-cap9r6oaw4jrovvcs/utlw@public.gmane.org \
--cc=fernando_b1-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=kaber-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netfilter-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sasaki.hirotaka-Zyj7fXuS5i5L9jVzuh4AOg@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).