diff options
| author | axis <qt-info@nokia.com> | 2010-06-24 09:58:42 (GMT) |
|---|---|---|
| committer | axis <qt-info@nokia.com> | 2010-06-24 09:58:42 (GMT) |
| commit | 06aaa4bc68a1ee10d2a7bb8de4928c92ce84546d (patch) | |
| tree | 7f20647d3f35434e44ec0a49473eb60544642f78 /src/network | |
| parent | 8d05bd74dcf13045a009bfd2008795f901b74fa8 (diff) | |
| download | Qt-06aaa4bc68a1ee10d2a7bb8de4928c92ce84546d.zip Qt-06aaa4bc68a1ee10d2a7bb8de4928c92ce84546d.tar.gz Qt-06aaa4bc68a1ee10d2a7bb8de4928c92ce84546d.tar.bz2 | |
Revert "Fixing race condition in qeventdispatcher_symbian.cpp code path"
This reverts commit 3a9ca8ba50a63e564c15023f65cbac36d365d309.
It's the wrong fix for the problem. The socket operations in the
select thread are not supposed to be thread safe. It is thread safe
between the select thread and the caller thread, but not if there are
more than one caller thread. Ensuring complete thread safety would
probably require fixes in other areas as well.
The correct fix is for the client to ensure that calls to the socket
registering functions are either serialized or contained within one
thread.
Task: QT-3496
RevBy: Aleksandar Sasha Babic
Diffstat (limited to 'src/network')
0 files changed, 0 insertions, 0 deletions