summaryrefslogtreecommitdiffhomepage
path: root/src/socket/ntapi_sc_getpeername_v2.c
diff options
context:
space:
mode:
authormidipix <writeonce@midipix.org>2016-05-10 14:01:16 -0400
committermidipix <writeonce@midipix.org>2016-05-14 07:18:24 -0400
commitf62cf86981025d5fb6f49b19db8153722c954f13 (patch)
tree3bafe335c58a78e51cd808687f7cf42aac0d27d9 /src/socket/ntapi_sc_getpeername_v2.c
parent25347d2a2820f20f30c8556baef36fe6e7067a79 (diff)
downloadntapi-f62cf86981025d5fb6f49b19db8153722c954f13.tar.bz2
ntapi-f62cf86981025d5fb6f49b19db8153722c954f13.tar.xz
__ntapi_pty_connect(): added resilience.
This patch accounts for zw_map_view_of_section() returning NT_STATUS_CONFLICTING_ADDRESSES (0xC0000018) due to third-party software thread creation upon process initialization. The conflict occurs when the address of the stack that is allocated for the third-party thread happens to coincide with the internal section address which was derived from the parent. As should be noted, and while we could decide to always reset ctx->section_addr prior to mapping the internal section, the advantage of the current solution (when acocmpanied by the wrapping calls to __ntapi_log_write) consists in the indication as to whether third-party thread creation had interfered with internal process initialization routines.
Diffstat (limited to 'src/socket/ntapi_sc_getpeername_v2.c')
0 files changed, 0 insertions, 0 deletions