Re: OK, so culicidae is *still* broken
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Date: 2017-04-15T21:30:18Z
Lists: pgsql-hackers
On 2017-04-15 17:24:54 -0400, Tom Lane wrote: > Andres Freund <andres@anarazel.de> writes: > > On 2017-04-15 17:09:38 -0400, Tom Lane wrote: > >> Why doesn't Windows' ability to map the segment into the new process > >> before it executes take care of that? > > > Because of ASLR of the main executable (i.e. something like PIE). > > Not following. Are you saying that the main executable gets mapped into > the process address space immediately, but shared libraries are not? Without PIE/ASLR we can somewhat rely on pgwin32_ReserveSharedMemoryRegion to find the space that PGSharedMemoryCreate allocated still unoccupied. If the main binary also uses ASLR, not just libraries/stack/other mappings, that's not guaranteed to be the case. But this probably needs somebody with actual windows expertise commenting. > I wonder whether we could work around that by just destroying the created > process and trying again if we get a collision. It'd be a tad > inefficient, but hopefully collisions wouldn't happen often enough to be a > big problem. That might work, although it's obviously not pretty. We could also just default to some out-of-the-way address for MapViewOfFileEx, that might also work. - Andres
Commits
-
Provide a way to control SysV shmem attach address in EXEC_BACKEND builds.
- 0d7591c67d68 9.2.21 landed
- fddc10146eb2 9.3.17 landed
- 07a990c6e7d1 9.4.12 landed
- bbd4a1b60b6e 9.5.7 landed
- a30f146db4e7 9.6.3 landed
- a74740fbd3bb 10.0 landed
-
Disable RandomizedBaseAddress on MSVC builds
- 7f3e17b4827b 9.4.0 cited