Issue 1441984: Multiple simultaneous sendtos on AF_UNIX socket broken. (original) (raw)

Created on 2006-03-02 19:29 by bdbrunswick, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg60878 - (view) Author: Brian Brunswick (bdbrunswick) Date: 2006-03-02 19:29
Using the same AF_UNIX socket to do multiple simultaneous calls to sendto from different threads, the messages get their to address mixed up. This is because of the use of a static per-socket buffer s->sock_addr in Modules/socketmodule.c function getsockaddrarg. It needs to be per thread.
msg109771 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2010-07-09 16:52
Brian to get this going forward could you provide a unit test for this?
msg109777 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2010-07-09 18:28
I'm almost certain that this has been fixed in issue 1544279. Setting to pending. Brian, if you disagree, you can still respond to this issue.
msg110821 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2010-07-19 22:29
Closing as noone has responded.
History
Date User Action Args
2022-04-11 14:56:15 admin set github: 42970
2010-07-19 22:29:12 BreamoreBoy set status: pending -> closedmessages: +
2010-07-09 18:28:17 skrah set status: open -> pending
2010-07-09 18:28:09 skrah set nosy: + skrahmessages: + resolution: duplicatesuperseder: Socket module is not thread-safestage: test needed -> resolved
2010-07-09 16:52:30 BreamoreBoy set nosy: + BreamoreBoymessages: + versions: + Python 3.1, Python 2.7, Python 3.2, - Python 2.6
2009-03-21 00:45:55 ajaksu2 set stage: test neededtype: behaviorversions: + Python 2.6, - Python 2.4
2006-03-02 19:29:45 bdbrunswick create