[issue13022] _multiprocessing.recvfd() doesn't check that file descriptor was actually received

Charles-François Natali added the comment: > The patch includes a test case, but like the other recently-added > tests for the function, it isn't guarded against > multiprocessing.reduction being unavailable. Issue #12981 has a > patch "skip_reduction.diff" (already in 3.3) to fix this, I'll a

[issue13022] _multiprocessing.recvfd() doesn't check that file descriptor was actually received

Roundup Robot added the comment: New changeset 21e7a55cb943 by Jesus Cea in branch '2.7': Close #13022: _multiprocessing.recvfd() doesn't check that file descriptor was actually received http://hg.python.org/cpython/rev/21e7a55cb943 New changeset 447770470d00 by Jesus Cea in branch '3.2': Clos

[issue13022] _multiprocessing.recvfd() doesn't check that file descriptor was actually received

Changes by Jesús Cea Avión : -- assignee: -> jcea nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue13022] _multiprocessing.recvfd() doesn't check that file descriptor was actually received

Changes by STINNER Victor : -- nosy: +neologix ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue13022] _multiprocessing.recvfd() doesn't check that file descriptor was actually received

Changes by David Watson : Added file: http://bugs.python.org/file23215/recvfd-skip-reduction-fix.diff ___ Python tracker ___ ___ Python-bugs-l

[issue13022] _multiprocessing.recvfd() doesn't check that file descriptor was actually received

New submission from David Watson : The function _multiprocessing.recvfd() calls recvmsg() and expects to receive a file descriptor in an SCM_RIGHTS control message, but doesn't check that such a control message is actually present. So if the sender sends data without an accompanying file descrip