[PATCH] forkables: hardlink without WRITE_ATTRIBUTES first

When the current process has renamed (to bin) a readonly dll, we get STATUS_TRANSACTION_NOT_ACTIVE for unknown reason when subsequently creating the forkable hardlink. A workaround is to open the original file with FILE_WRITE_ATTRIBUTES access, but that fails with permission denied for users not ow

Re: [PATCH] forkables: hardlink without WRITE_ATTRIBUTES first

On Mar 10 11:32, Michael Haubenwallner wrote: > When the current process has renamed (to bin) a readonly dll, we get > STATUS_TRANSACTION_NOT_ACTIVE for unknown reason when subsequently > creating the forkable hardlink. A workaround is to open the original > file with FILE_WRITE_ATTRIBUTES access,