Re: [PATCH v2 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

On 5/4/2018 3:12 AM, Andrew Morton wrote: On Tue, 17 Apr 2018 16:13:48 +0530 Chintan Pandya wrote: Client can call vunmap with some intermediate 'addr' which may not be the start of the VM area. Entire unmap code works with vm->vm_start which is proper but debug

Re: [PATCH v2 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

On 5/4/2018 3:12 AM, Andrew Morton wrote: On Tue, 17 Apr 2018 16:13:48 +0530 Chintan Pandya wrote: Client can call vunmap with some intermediate 'addr' which may not be the start of the VM area. Entire unmap code works with vm->vm_start which is proper but debug object API is called with

Re: [PATCH v2 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

On Tue, 17 Apr 2018 16:13:48 +0530 Chintan Pandya wrote: > Client can call vunmap with some intermediate 'addr' > which may not be the start of the VM area. Entire > unmap code works with vm->vm_start which is proper > but debug object API is called with 'addr'. This >

Re: [PATCH v2 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

On Tue, 17 Apr 2018 16:13:48 +0530 Chintan Pandya wrote: > Client can call vunmap with some intermediate 'addr' > which may not be the start of the VM area. Entire > unmap code works with vm->vm_start which is proper > but debug object API is called with 'addr'. This > could be a problem within

Re: [PATCH v2 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

On 5/1/2018 4:34 AM, Andrew Morton wrote: should check for it and do a WARN_ONCE so it gets fixed. Yes, that was an idea in discussion but I've been suggested that it could be intentional. But since you are raising this, I will try to dig once again and share a patch with WARN_ONCE if

Re: [PATCH v2 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

On 5/1/2018 4:34 AM, Andrew Morton wrote: should check for it and do a WARN_ONCE so it gets fixed. Yes, that was an idea in discussion but I've been suggested that it could be intentional. But since you are raising this, I will try to dig once again and share a patch with WARN_ONCE if

Re: [PATCH v2 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

On Tue, 17 Apr 2018 16:13:48 +0530 Chintan Pandya wrote: > Client can call vunmap with some intermediate 'addr' > which may not be the start of the VM area. Entire > unmap code works with vm->vm_start which is proper > but debug object API is called with 'addr'. This >

Re: [PATCH v2 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

On Tue, 17 Apr 2018 16:13:48 +0530 Chintan Pandya wrote: > Client can call vunmap with some intermediate 'addr' > which may not be the start of the VM area. Entire > unmap code works with vm->vm_start which is proper > but debug object API is called with 'addr'. This > could be a problem within

[PATCH v2 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

Client can call vunmap with some intermediate 'addr' which may not be the start of the VM area. Entire unmap code works with vm->vm_start which is proper but debug object API is called with 'addr'. This could be a problem within debug objects. Pass proper start address into debug object API.

[PATCH v2 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

Client can call vunmap with some intermediate 'addr' which may not be the start of the VM area. Entire unmap code works with vm->vm_start which is proper but debug object API is called with 'addr'. This could be a problem within debug objects. Pass proper start address into debug object API.