handling IRPs 17: Call to Action and Resources

centos-com

于 2013-06-15 17:42:58 发布

阅读量836

点赞数

CC 4.0 BY-SA版权

分类专栏：驱动开发

本文链接：https://blog.youkuaiyun.com/sunboyhch/article/details/9102419

驱动开发专栏收录该内容

27 篇文章

订阅专栏

本文为驱动开发者提供了详细的行动号召及资源指南，强调了在编写驱动程序时如何正确处理IRP（I/O请求包）。主要内容包括：如何在所有IoCompletion例程中返回正确的状态代码；何时应返回STATUS_PENDING；如何使用DriverVerifier捕获IRP处理错误等。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Call to Action and Resources

Call to action for driver developers:

· Return STATUS_CONTINUE_COMPLETION or STATUS_MORE_PROCESSING_REQUIRED from all IoCompletion routines.

· Understand when to return STATUS_PENDING for an IRP. Return STATUS_PENDING only if you have called theIoMarkIrpPending macro for the IRP, and conversely, callIoMarkIrpPending for an IRP only if you will return STATUS_PENDING.

· Test the value of the Irp->PendingReturned flag in IoCompletion routines to optimize post-processing of IRPs.

· Understand the difference between error status and warning status, and what data the IRP contains for each type of status.

· Use Driver Verifier to catch errors in IRP handling, and use debugger extensions to understand how individual IRPs are processed.