Re: [PATCH v10 13/17] mm: vmalloc: add flag preventing guard hole allocation

2015-01-30 Thread Andrey Ryabinin
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

Re: [PATCH v10 13/17] mm: vmalloc: add flag preventing guard hole allocation

2015-01-30 Thread Andrey Ryabinin
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

Re: [PATCH v10 13/17] mm: vmalloc: add flag preventing guard hole allocation

2015-01-29 Thread Andrew Morton
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

[PATCH v10 13/17] mm: vmalloc: add flag preventing guard hole allocation

2015-01-29 Thread Andrey Ryabinin
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

[PATCH v10 13/17] mm: vmalloc: add flag preventing guard hole allocation

2015-01-29 Thread Andrey Ryabinin
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

Re: [PATCH v10 13/17] mm: vmalloc: add flag preventing guard hole allocation

2015-01-29 Thread Andrew Morton
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