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@xxxxxxxxxxxxx> Signed-off-by: Fernando Luis Vazquez Cao <fernando@xxxxxxxxxxxxx> --- 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. .SH EXAMPLE An example of the use of .BR sendto () -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html