{"id":199,"date":"2010-04-18T00:28:43","date_gmt":"2010-04-18T09:28:43","guid":{"rendered":"\/blog\/?p=199"},"modified":"2023-09-21T09:39:11","modified_gmt":"2023-09-21T00:39:11","slug":"ddk-irp%ea%b0%80-%eb%b9%84%eb%8f%99%ea%b8%b0%ec%a0%81%ec%9c%bc%eb%a1%9c-%ec%b2%98%eb%a6%ac%eb%90%98%ec%96%b4%ec%95%bc-%ed%95%a0%eb%95%8c","status":"publish","type":"post","link":"https:\/\/hasu0707.duckdns.org\/blog\/?p=199","title":{"rendered":"[DDK] IRP\uac00 \ube44\ub3d9\uae30\uc801\uc73c\ub85c \ucc98\ub9ac\ub418\uc5b4\uc57c \ud560\ub54c"},"content":{"rendered":"\n
\uc694\uc998 \uac01\uc885 \ubc88\uc5ed\uc11c\ub4e4\uc774 \ub9c8\uc74c\uc5d0 \uc548\ub4e4\uc5b4\uc11c DDK\uc640 WDK \ubb38\uc11c\ub97c \ubcf4\uba74\uc11c

\uacf5\ubd80\ub97c \ud558\uace0 \n\uc788\ub2e4.

\uc601\uc5b4\uae34 \ud55c\ub370, \uac70\ubd80\uac10\uc5c6\uc774 \ubcf4\ub2c8\uae4c \uc601 \uac70\ub9ac\uac00 \uba40\uc9c4 \uc54a\uc740\uac83 \uac19\ub2e4.

\uc775\uc219\ud574\uc9c0\uba74 \uc601\uc5b4\ub3c4 \ub298\uace0 \uc88b\uaca0\uc9c0,, - \n_-;

\uc77c\ub2e8 \uc815\ub9ac\ud574\ubcf4\uba74, Queuing\uc744 \ud55c\ub2e4.

\uc65c\ub0d0? \ube44\ub3d9\uae30\uc801\uc73c\ub85c \ucc98\ub9ac\ud574\uc57c\ud558\uba74 \ud050\uc5d0 \uc313\uc544\ub193\uc558\ub2e4\uac00 \n\ucc98\ub9ac\ud574\uc57c\ud55c\ub2e4.

\uadf8\ub7ec\uae30\uc704\ud574\uc11c Queuing\uc744 \ud574\uc57c\ud558\ub294\ub370,

\uc77c\ub2e8 \ub0b4\uc6a9\uc744 \ubcf4\uba74 \uc774\ub807\ub2e4.

<\/div>\n

Force Pending I\/O Requests<\/h1>\n

The Force Pending I\/O Requests option randomly returns \nSTATUS_PENDING in response to a driver's calls to IoCallDriver<\/b><\/mshelp:link>. \nThis option tests the driver's logic for responding to STATUS_PENDING return \nvalues from IoCallDriver<\/b>.<\/p>\n

This option is supported only on Windows Vista and later \nversions of the Windows operating system.<\/p>\n

Caution<\/b>  Do not use this option on a driver unless you have \ndetailed knowledge of the operation of the driver and have verified that the \ndriver is designed to handle STATUS_PENDING return values from all<\/i> of its \ncalls to IoCallDriver<\/b>. Running this option on a driver that is not \ndesigned to handle STATUS_PENDING from all calls can result in crashes, memory \ncorruptions, and unusual system behavior that can be difficult to debug or \ncorrect.<\/p>\n

Why Use Force Pending I\/O Requests?<\/h4>\n

Higher-level drivers in a driver stack call IoCallDriver<\/b><\/mshelp:link> \nto pass an IRP down to lower-level drivers in the driver stack. The driver \ndispatch routine in the lower-level driver that receives the IRP can either \ncomplete the IRP immediately or return STATUS_PENDING and complete the IRP at a \nlater time. <\/p>\n

Typically, the caller must be prepared to handle either \noutcome. However, because most dispatch routines handle the IRP immediately, the \nSTATUS_PENDING logic in the caller is not often exercised and serious logic \nerrors might not be detected. The Force Pending I\/O Requests option intercepts \ncalls to IoCallDriver<\/b> and returns STATUS_PENDING to test the calling \ndriver's infrequently used logic.<\/p>\n

When do you use Force Pending I\/O Requests?<\/h4>\n

Before running this test, review the driver design and \nsource code and confirm that the driver is intended to handle STATUS_PENDING \nfrom all<\/i> of its IoCallDriver<\/b><\/mshelp:link> \n<\/b>calls.<\/p>\n

Many drivers are not designed to handle STATUS_PENDING on \nall calls to IoCallDriver<\/b>. They might be sending the IRP to a particular \nwell-known driver that is guaranteed to complete the IRP immediately. Sending \nSTATUS_PENDING to a driver that does not handle it can cause driver and system \ncrashes and memory corruption.<\/p>\n

How should drivers handle STATUS_PENDING?<\/h4>\n

The higher-level driver that calls IoCallDriver<\/b><\/mshelp:link> \n<\/b>must handle a STATUS_PENDING return value as follows:<\/p>\n

\n