| Previous | Next |
| STATUS_FLT_INVALID_NAME_REQUEST | STATUS_FLT_NOT_INITIALIZED |
STATUS_FLT_NOT_SAFE_TO_POST_OPERATION
STATUS_FLT_NOT_SAFE_TO_POST_OPERATION is a safety boundary, not a request to keep queuing work until it succeeds. Filter Manager has determined that posting the current completion to a worker could deadlock the I/O path.
Keep the post-operation work minimal and make ownership explicit. If the operation needs deferred processing, use a design that is valid for the current callback and operation rather than bypassing the safety result with an ad-hoc worker queue. A deferred task must not hold state that prevents the lower stack from completing the same I/O.
What to inspect
- The callback phase and any locks, resources, or file-system callbacks already active on the stack.
- The completion context lifetime and whether it can be released immediately.
- Whether the policy can use a different operation phase or a documented asynchronous API.
Writing callback routines | Filter Manager concepts | NTSTATUS reference
Looking for a different code? Search another status or error code.