タグは Microsoft によって監視されません。
situmononegaisimasu
Subject: Request for Official Windows API Guarantee — Atomic Revocation and TerminateProcess Invocation
Hello Microsoft Windows Developer Support,
We are developing a Windows 11 application that manages the lifetime and termination of processes using original process handles and strict safety controls.
We would like clarification of the officially supported Windows API guarantees concerning TerminateProcess.
Our design requires both of the following conditions:
- Once a revocation becomes effective, a
TerminateProcessinvocation that has not yet begun must not be allowed to begin.
Even if a native API invocation stalls indefinitely, the revocation and deadline-management path must remain independently operational.
We have reviewed documented synchronization mechanisms, including Interlocked operations, critical sections, SRW locks, cancellation APIs, asynchronous operations, and separate execution threads or processes.
We have not identified a documented mechanism that guarantees both conditions simultaneously.
Could you please clarify:
Does Windows provide a documented mechanism that atomically associates an application-controlled revocation state with the actual commencement of a TerminateProcess invocation?
We are specifically seeking a documented API contract, rather than experimental observations or best-effort synchronization techniques.
If no supported mechanism provides these guarantees, confirmation of that documentation limitation would also be helpful.
Please provide relevant Microsoft documentation or an authoritative technical reference where possible.
Thank you.
<モデレーター注>
重複した質問内容(2重ペースト)を整理させて頂きました。
質問は、第三者を含めて混乱しない様に、一問一答形式にしてください。
1つのスレッド内に複数の質問を投稿しない
回答内容が発散してしまうことを回避する為に、複数の質問内容は削除させて頂きました。