[PATCH 0/6] Protect fork() against dll- and exe-updates.

Michael Haubenwallner michael.haubenwallner@ssi-schaefer.com
Wed Mar 30 19:04:00 GMT 2016

On 03/30/2016 08:55 PM, Daniel Colascione wrote:
> On 03/30/2016 11:53 AM, Michael Haubenwallner wrote:
>> Hi,
>> this is the updated and split series of patches to use hardlinks
>> for creating the child process by fork(), in reply to
>> https://cygwin.com/ml/cygwin-developers/2016-01/msg00002.html
>> https://cygwin.com/ml/cygwin-developers/2016-03/msg00005.html
>> http://thread.gmane.org/gmane.os.cygwin.devel/1378
>> Thanks for review!
>> /haubi/
> Creating a new process now requires a write operation on the filesystem
> hosting the binary? Seriously? I don't think that's worth it no matter
> the other benefits.

Only if the original binaries necessary to create the new child process
by fork() are not available any more - and the /var/run/cygfork/
directory does exist and is on NTFS.  I do prefer a working fork() even
when updating dlls and executables while the parent process is running.


More information about the Cygwin-patches mailing list