| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8011834 | 8 | Nils Eliasson | P4 | Closed | Fixed | b85 |
| JDK-8185863 | 7u171 | David Buck | P4 | Resolved | Fixed | b01 |
| JDK-8011275 | hs25 | Nils Eliasson | P4 | Closed | Fixed | b26 |
Dan discovered a faulty Winsock initialization code in src/os/windows/vm/os_windows.cpp:initSock().
Copied from Dan's email, the line number may not be accurate.
This block is supposed to only allow one thread to init the
WinSock2 stuff. Consider this scenario:
- thread-1 makes it through line 4638 so it owns the mutex
- thread-2 makes it past line 4635 so it calls mutexInit()
on the mutex that thread-1 owns; does this mess up the
mutex?
- thread-1 finishes initializing WinSock2 and gets to line 4647
where it calls mutexUnlock() on the mutex; does this work when
thread-2 has called mutexInit() on the mutex?
Copied from Dan's email, the line number may not be accurate.
This block is supposed to only allow one thread to init the
WinSock2 stuff. Consider this scenario:
- thread-1 makes it through line 4638 so it owns the mutex
- thread-2 makes it past line 4635 so it calls mutexInit()
on the mutex that thread-1 owns; does this mess up the
mutex?
- thread-1 finishes initializing WinSock2 and gets to line 4647
where it calls mutexUnlock() on the mutex; does this work when
thread-2 has called mutexInit() on the mutex?
- backported by
-
JDK-8185863 Faulty Winsock initialization code in src/os/windows/vm/os_windows.cpp
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
- duplicates
-
JDK-8010190 os_windows missing winsock initialization on some paths
-
- Closed
-