Get buffer size of ExAllocatePoolWithTag

Hi,

Is there a way to get the size of a buffer allocated with
ExAllocatePoolWithTag without having to put your own wrapper around it.
Just native support?

TIA!!

Why in the world would you want this? Either your driver allocated the
buffer and should know its size, or the buffer was passed to you with a
size. Any other case is bad design, for instance you should not be playing
with buffers you don't own, and you should not assume anything about the
size of a buffer passed to you beyond what the caller provides.


--
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply



"David F." <> wrote in message
news:56A551A3-E716-4B32-9E98-...
> Hi,
>
> Is there a way to get the size of a buffer allocated with
> ExAllocatePoolWithTag without having to put your own wrapper around it.
> Just native support?
>
> TIA!!
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4713 (20091223) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4713 (20091223) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

realloc override without having to have #if defined(WIN_DDK_BUILD) around
sections of code that is universal.

"Don Burn" <> wrote in message
news:...
> Why in the world would you want this? Either your driver allocated the
> buffer and should know its size, or the buffer was passed to you with a
> size. Any other case is bad design, for instance you should not be
> playing with buffers you don't own, and you should not assume anything
> about the size of a buffer passed to you beyond what the caller provides.
>
>
> --
> Don Burn (MVP, Windows DKD)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
>
>
>
> "David F." <> wrote in message
> news:56A551A3-E716-4B32-9E98-...
>> Hi,
>>
>> Is there a way to get the size of a buffer allocated with
>> ExAllocatePoolWithTag without having to put your own wrapper around it.
>> Just native support?
>>
>> TIA!!
>>
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus
>> signature database 4713 (20091223) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4713 (20091223) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>

You're on your own on this one, we don't have that kind of insight into the
pool allocator in kernel mode.

-scott

--
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com


"David F." <> wrote in message
news:36DEBF22-9060-460C-879F-...
> realloc override without having to have #if defined(WIN_DDK_BUILD) around
> sections of code that is universal.
>
> "Don Burn" <> wrote in message
> news:...
>> Why in the world would you want this? Either your driver allocated the
>> buffer and should know its size, or the buffer was passed to you with a
>> size. Any other case is bad design, for instance you should not be
>> playing with buffers you don't own, and you should not assume anything
>> about the size of a buffer passed to you beyond what the caller provides.
>>
>>
>> --
>> Don Burn (MVP, Windows DKD)
>> Windows Filesystem and Driver Consulting
>> Website: http://www.windrvr.com
>> Blog: http://msmvps.com/blogs/WinDrvr
>> Remove StopSpam to reply
>>
>>
>>
>> "David F." <> wrote in message
>> news:56A551A3-E716-4B32-9E98-...
>>> Hi,
>>>
>>> Is there a way to get the size of a buffer allocated with
>>> ExAllocatePoolWithTag without having to put your own wrapper around it.
>>> Just native support?
>>>
>>> TIA!!
>>>
>>>
>>>
>>> __________ Information from ESET NOD32 Antivirus, version of virus
>>> signature database 4713 (20091223) __________
>>>
>>> The message was checked by ESET NOD32 Antivirus.
>>>
>>> http://www.eset.com
>>>
>>>
>>>
>>
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus
>> signature database 4713 (20091223) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>>
>

"David F." <> wrote in message
news:36DEBF22-9060-460C-879F-...
> realloc override without having to have #if defined(WIN_DDK_BUILD) around
> sections of code that is universal.

Make your own allocator, or change design.
--pa


> "Don Burn" <> wrote in message
> news:...
>> Why in the world would you want this? Either your driver allocated the
>> buffer and should know its size, or the buffer was passed to you with a
>> size. Any other case is bad design, for instance you should not be
>> playing with buffers you don't own, and you should not assume anything
>> about the size of a buffer passed to you beyond what the caller provides.
>>
>> --
>> Don Burn (MVP, Windows DKD)
>> Windows Filesystem and Driver Consulting
>> Website: http://www.windrvr.com
>> Blog: http://msmvps.com/blogs/WinDrvr
>> Remove StopSpam to reply
>>
>>
>>
>> "David F." <> wrote in message
>> news:56A551A3-E716-4B32-9E98-...
>>> Hi,
>>>
>>> Is there a way to get the size of a buffer allocated with
>>> ExAllocatePoolWithTag without having to put your own wrapper around it.
>>> Just native support?
>>>
>>> TIA!!
>>>