On 01/30/2015 02:12 AM, Andrew Morton wrote:
> On Thu, 29 Jan 2015 18:11:57 +0300 Andrey Ryabinin
> wrote:
>
>> For instrumenting global variables KASan will shadow memory
>> backing memory for modules. So on module loading we will need
>> to allocate shadow memory and map it at exact virtual
On 01/30/2015 02:12 AM, Andrew Morton wrote:
On Thu, 29 Jan 2015 18:11:57 +0300 Andrey Ryabinin a.ryabi...@samsung.com
wrote:
For instrumenting global variables KASan will shadow memory
backing memory for modules. So on module loading we will need
to allocate shadow memory and map it at
On Thu, 29 Jan 2015 18:11:57 +0300 Andrey Ryabinin
wrote:
> For instrumenting global variables KASan will shadow memory
> backing memory for modules. So on module loading we will need
> to allocate shadow memory and map it at exact virtual address.
I don't understand. What does "map it at
For instrumenting global variables KASan will shadow memory
backing memory for modules. So on module loading we will need
to allocate shadow memory and map it at exact virtual address.
__vmalloc_node_range() seems like the best fit for that purpose,
except it puts a guard hole after allocated
For instrumenting global variables KASan will shadow memory
backing memory for modules. So on module loading we will need
to allocate shadow memory and map it at exact virtual address.
__vmalloc_node_range() seems like the best fit for that purpose,
except it puts a guard hole after allocated
On Thu, 29 Jan 2015 18:11:57 +0300 Andrey Ryabinin a.ryabi...@samsung.com
wrote:
For instrumenting global variables KASan will shadow memory
backing memory for modules. So on module loading we will need
to allocate shadow memory and map it at exact virtual address.
I don't understand. What
6 matches
Mail list logo