| Previous | Next |
| STATUS_PENDING | STATUS_MORE_ENTRIES |
STATUS_REPARSE
A name-resolution control result
STATUS_REPARSE is not a normal application-level failure such as “file not found.” The NTSTATUS definition says that the Object Manager must perform a reparse because resolving the current name reached a symbolic link. In other words, lookup has encountered a boundary where the current name is no longer the final object path.
The useful question is whether the caller intended to follow the link. A security-sensitive operation can deliberately request inspection of the link object, while an ordinary open usually expects the namespace resolver to continue toward its target. Treating the status as a transient I/O error loses that distinction.
Diagnostic boundary
- Record the original native name, root handle if one was supplied, and the path component at which resolution changed.
- Determine whether the operation intended to open the reparse object itself or its target.
- Keep the reparse tag and target data with the trace; the tag identifies the handler and data format.
- Do not retry an open blindly when the caller is supposed to enforce a path-boundary policy.
References
Looking for a different code? Search another status or error code.