Re: ntdll: enable CreateRemoteThread and RtlCreateUserThread for remote processes

[Alexandre Julliard]

"Dan Kegel"  writes:
> I'm afraid I don't quite understand.  What's wrong with interrupting a thread
> holding a lock?  Could that make cloning a new thread deadlock?

One problem is that many locks have to be acquired in a specific order
to avoid deadlocks, and since you don't know which locks the thread is
already holding you can't guarantee the order. The other problem is
that you can't guarantee that critical sections are in a valid state
since the thread could be interrupted in the middle of a crit section
call.