diff options
author | Corinna Vinschen <corinna@vinschen.de> | 2022-12-01 23:33:14 +0300 |
---|---|---|
committer | Corinna Vinschen <corinna@vinschen.de> | 2022-12-02 00:34:53 +0300 |
commit | 30add3e6b3e3211b3e2d4a093f45bee5c6e24b8b (patch) | |
tree | 6395f10d90550788a94fe37abb53c12f830dda53 /winsup/cygwin/external.cc | |
parent | e358f8d12f1537a7d0509984207a700205b2c20f (diff) |
Cygwin: exec: don't access cygheap before it's initialized
This is a long-standing thinko.
When you exec a process, dll_crt0_0 in the child process calls
child_info_spawn::handle_spawn(). handle_spawn() initialises the
cygheap.
Now consider calling strace. Strace is a non-Cygwin process dynamically
loading cygwin1.dll via LoadLibrary. This in turn initializes the DLL:
- dll_crt0_0 finds that the process it attaches to has been exec'd, so
child_info_spawn::handle_spawn() is called.
- If the DLL is being dynamically loaded, handle_spawn() calls
child_info_spawn::get_parent_handle(). This in turn tries to set
the moreinfo->myself_pinfo value inside the cygheap to NULL.
- However, at this time, the cygheap has not yet been initialized. This
only occurs in the cygheap_fixup_in_child() call after get_parent_handle()
returns.
--> SEGV
This thinko never had a negative side effect, because the cygheap was
pre-allocated at DLL load time until commit 2f9b8ff00cce ("Cygwin:
decouple cygheap from Cygwin DLL"). With 2f9b8ff00cce, the cygheap
actually doesn't exist until after the call to cygheap_fixup_in_child().
Fix this problem by moving the assignment after the call to
cygheap_fixup_in_child().
Fixes: 3de7be4c1deb ("* DevNotes: Add entry cgf-000007. [...]")
Fixes: 2f9b8ff00cce ("Cygwin: decouple cygheap from Cygwin DLL")
Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
Diffstat (limited to 'winsup/cygwin/external.cc')
0 files changed, 0 insertions, 0 deletions