I'm not entirely sure, how debug objects are really useful in vmalloc framework. I'm assuming they are useful in some ways. So, there are 2 issues in that. First patch is avoiding possible race scenario and second patch passes _proper_ args in debug object APIs. Both these patches can help debug objects to be in consistent state. We've observed some list corruptions in debug objects. However, no claims that these patches will be fixing them. If one has an opinion that debug object has no use in vmalloc framework, I would raise a patch to remove them from the vunmap leg. Below 2 patches are rebased over tip + my other patch in review "[PATCH v2] mm: vmalloc: Clean up vunmap to avoid pgtable ops twice" Chintan Pandya (2): mm: vmalloc: Avoid racy handling of debugobjects in vunmap mm: vmalloc: Pass proper vm_start into debugobjects >From V1->V2: - Incorporated Anshuman's comment about missing corrections in vm_unmap_ram() mm/vmalloc.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) -- Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc., is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
