Re: problem to understand behavior of I/O manager

- deliver the IRP to the IOCP's queue if any
- queue a user APC using KAPC at IRPs tail if Read/WriteFileEx were
used

Do these mean that, if Win32 has already reported ERROR_PENDING
to the application, the kernel cannot later run out of memory
when trying to report the completion of the I/O?

The kernel itself will not, but the particular driver can.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com

.

Relevant Pages

  • Re: problem to understand behavior of I/O manager
    ... - queue a user APC using KAPC at IRPs tail if Read/WriteFileEx were used ... if Win32 has already reported ERROR_PENDING ... when trying to report the completion of the I/O? ...
    (microsoft.public.development.device.drivers)
  • Oops with "linux-2.4.29"
    ... Kernel "linux-2.4.29" oopses irregularly. ... We are running software RAID1 on two SCSI hard disks, ... I didn't have the time to write a bug report ... linux kernel 2.4.29 oops ext3 I/O high load SCSI ...
    (Linux-Kernel)
  • [RFC][PATCH] Update REPORTING-BUGS (rev. 2)
    ... want to report a kernel bug for the first time. ... Having a standardized bug report form makes it easier for you not to ... +three mailing lists simultaneously, if you think that it is necessry. ...
    (Linux-Kernel)
  • [BUG] Oops in 2.6.24-rc2-mm1
    ... I am new to the kernel and this is my first report. ... If I had made any mistakes with this report, ... # Firmware Drivers ... # SCSI support type ...
    (Linux-Kernel)
  • Re: Updates caused problems...
    ... > 1) Kernel 2.6.26.3-29.f9.i686: ... > 3) The livna issue is a seperate issue - and is not a show-stopper as I have ... and remains and is unique to Fedora ... > perhaps a link, perhaps what to report, with what expected information, ...
    (Fedora)