paged memory and system work items

NTFSD
1

I have my Read Completion routine kick off a Work Item (yes, I know :slight_smile: if it
is called at Dispatch level, which is most of the time.

I thought that the Work Item should be able to access Paged Pool since it is
not executing at Dispatch level, but it keeps blue screening. Am I wrong?

Thanks.

2

Yes, you should be running at PASSIVE_LEVEL.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Neil Weicher
Sent: Tuesday, July 17, 2007 17:48
To: Windows File Systems Devs Interest List
Subject: [ntfsd] paged memory and system work items

I have my Read Completion routine kick off a Work Item (yes, I know :slight_smile:
if it
is called at Dispatch level, which is most of the time.

I thought that the Work Item should be able to access Paged Pool since
it is
not executing at Dispatch level, but it keeps blue screening. Am I
wrong?

Thanks.

Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@evitechnology.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

> I thought that the Work Item should be able to access Paged Pool since it

is

Yes, you right, it is executed at PASSIVE_LEVEL.

I have my Read Completion routine kick off a Work Item (yes, I know :slight_smile: if
it …
but it keeps blue screening.

I think you touch something that has been freed during completion after you
postpone execution but before you work item has been called, you should
defer completion by returning STATUS_MORE_PROCESSING_REQUIRED, from
completion routine at DISPATCH_LEVEL, if you want to touch something that
you can’t block from deleting( i.e. memory from pool allocated by another
driver, file object etc. ), but you should also mark the IRP as pending and
return STATUS_PENDING from dispatch routine or else when you call
IoCompleteRequest in your WorkItem the request won’t be completed properly
if the IRP has not been marked as pending and STATUS_PENDING was not
returned. But remember - you can’t postpone Irp in another thread for FSD
request if “top level Irp” is not NULL, so after returning STATUS_PENDING
call the lower device in the same thread.

–
Slava Imameyev, xxxxx@hotmail.com

“Neil Weicher” wrote in message news:xxxxx@ntfsd…
>I have my Read Completion routine kick off a Work Item (yes, I know :slight_smile: if
>it is called at Dispatch level, which is most of the time.
>
> I thought that the Work Item should be able to access Paged Pool since it
> is not executing at Dispatch level, but it keeps blue screening. Am I
> wrong?
>
> Thanks.
>
>