I’m running with the verifier enabled on everything
but low resource simulation, no special pool,
and no pool tracking, and I’ve run into
something odd on XP sp1.
I have a TDI client that is sending an irp/mdl
that maps 0x820 bytes. The mdl looks fine,
the irp looks fine.
However, at IPLargeXmit+0x163 the verifier
says that tcpip is trying to allocate 0 bytes.
nt!RtlpBreakWithStatusInstruction
nt!KiBugCheckDebugBreak+0x19
nt!KeBugCheck2+0x46d
nt!KeBugCheckEx+0x19
nt!ExAllocatePoolSanityChecks+0x5a
nt!VeAllocatePoolWithTagPriority+0x15
nt!VerifierAllocatePoolWithTagPriority+0x45
tcpip!IPLargeXmit+0x163
tcpip!TCPSend+0x342
tcpip!TdiSend+0x193
tcpip!TCPSendData+0x81
tcpip!TCPDispatchInternalDeviceControl+0x4a
Is this something that is “known” and I just
shouldn’t use verifier on tcpip?
I’m *very* confused. Any hints would be appreciated.
Thanks.