multiprocessing.Connection endianness issue

[neologix]

BPO	12996
Nosy	@vstinner
Files	multiprocessing_conn_endianness.diff

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2011-09-20.18:27:21.798>
created_at = <Date 2011-09-16.18:40:54.501>
labels = ['type-bug', 'library']
title = 'multiprocessing.Connection endianness issue'
updated_at = <Date 2011-09-20.18:27:21.797>
user = 'https://bugs.python.org/neologix'

bugs.python.org fields:

activity = <Date 2011-09-20.18:27:21.797>
actor = 'neologix'
assignee = 'none'
closed = True
closed_date = <Date 2011-09-20.18:27:21.798>
closer = 'neologix'
components = ['Library (Lib)']
creation = <Date 2011-09-16.18:40:54.501>
creator = 'neologix'
dependencies = []
files = ['23171']
hgrepos = []
issue_num = 12996
keywords = ['patch', 'needs review']
message_count = 4.0
messages = ['144148', '144236', '144239', '144342']
nosy_count = 3.0
nosy_names = ['vstinner', 'neologix', 'python-dev']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue12996'
versions = ['Python 3.3']

[neologix]

Since the rewrite in pure Python of multiprocessing.Connection (issue bpo-11743), multiprocessing.Connection sends and receives the length of the data (used as header) in host byte order.
This will break if the connection's endpoints are on machine with different endianness.
Patch attached (it also removes an unnecessary computation of the length of the data being sent).

[vstinner]

"Since the rewrite in pure Python of multiprocessing.Connection (issue bpo-11743), multiprocessing.Connection sends and receives the length of the data (used as header) in host byte order."

I don't think so, the C code uses also the host endian. This issue is a feature request.

I don't know if anyone uses multiprocessing on different hosts (because it doesn't work currently).

If you would like to support using multiprocessing on different hosts, it should be documented in multiprocessing doc.

[neologix]

"Since the rewrite in pure Python of multiprocessing.Connection (issue bpo-11743), multiprocessing.Connection sends and receives the length of the data (used as header) in host byte order."

I don't think so, the C code uses also the host endian. This issue is a feature request.

No.
http://hg.python.org/cpython/file/5deecc04b7a2/Modules/_multiprocessing/socket_connection.c
In conn_send_string():
"""
/* The "header" of the message is a 32 bit unsigned number (in
network order) which specifies the length of the "body". If
the message is shorter than about 16kb then it is quicker to
combine the "header" and the "body" of the message and send
them at once. */
[...]
*(UINT32*)message = htonl((UINT32)length);
"""

in conn_recv_string():
"""
ulength = ntohl(ulength);
"""

I don't know if anyone uses multiprocessing on different hosts (because it doesn't work currently).

If you would like to support using multiprocessing on different hosts, it should be documented in multiprocessing doc.

It does work, it's even documented ;-)

http://docs.python.org/dev/library/multiprocessing.html#multiprocessing-managers
"""
A manager object returned by Manager() controls a server process which
holds Python objects and allows other processes to manipulate them
using proxies.
[...]
Server process managers are more flexible than using shared memory
objects because they can be made to support arbitrary object types.
Also, a single manager can be shared by processes on different
computers over a network. They are, however, slower than using shared
memory.
"""

Managers use multiprocessing.connection to serialize data and send
them over a socket:
http://hg.python.org/cpython/file/5deecc04b7a2/Lib/multiprocessing/managers.py
"""

# Mapping from serializer name to Listener and Client types

listener_client = {
'pickle' : (connection.Listener, connection.Client),
'xmlrpclib' : (connection.XmlListener, connection.XmlClient)
}
"""

Yeah, Python's awesome :-)

[python-dev]

New changeset 9c1c81d24e23 by Charles-François Natali in branch 'default':
Issue bpo-12996: multiprocessing.connection: transmit the header in network byte
http://hg.python.org/cpython/rev/9c1c81d24e23