Can I use safe string functions at raised IRQL?

The WDK states that these functions (RtlStringXXX) must only be used
at IRQL passive level. I need to perform some string operations at
DPC level and all of my strings exist in non paged pool. Is it ok to
use these functions at IRQLs > passive level in these cases? I
noticed that the implementations of all the safe string functions are
in ntstrsafe.h and they are not wrapped in a #pragma PAGED_CODE
section so I suspect that this is ok. Are there any dangers of using
these functions at raised IRQL that I may not be aware of?

Doron
Wed Feb 07 21:31:10 CST 2007

why do you need to do string management at DPC? b/c of a lock or because
your hardware is sending you strings?

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"DavidP" <icrashedagain@hotmail.com> wrote in message
news:1170881520.299535.304950@k78g2000cwa.googlegroups.com...
> The WDK states that these functions (RtlStringXXX) must only be used
> at IRQL passive level. I need to perform some string operations at
> DPC level and all of my strings exist in non paged pool. Is it ok to
> use these functions at IRQLs > passive level in these cases? I
> noticed that the implementations of all the safe string functions are
> in ntstrsafe.h and they are not wrapped in a #pragma PAGED_CODE
> section so I suspect that this is ok. Are there any dangers of using
> these functions at raised IRQL that I may not be aware of?
>

DavidP
Thu Feb 08 01:55:02 CST 2007

I need to do some simple string manipulation in dispatch routines that
may run at DPC level. The strings are guaranteed to be in non paged
pool, but my IRQL may be 0 to 2.