mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-16 09:13:55 +08:00
mm/cma: make kmemleak ignore CMA regions
kmemleak will add allocations as objects to a pool. The memory allocated for each object in this pool is periodically searched for pointers to other allocated objects. This only works for memory that is mapped into the kernel's virtual address space, which happens not to be the case for most CMA regions. Furthermore, CMA regions are typically used to store data transferred to or from a device and therefore don't contain pointers to other objects. Without this, the kernel crashes on the first execution of the scan_gray_list() because it tries to access highmem. Perhaps a more appropriate fix would be to reject any object that can't map to a kernel virtual address? [akpm@linux-foundation.org: add comment] [akpm@linux-foundation.org: fix comment, per Catalin] [sfr@canb.auug.org.au: include linux/io.h for phys_to_virt()] Signed-off-by: Thierry Reding <treding@nvidia.com> Cc: Michal Nazarewicz <mina86@mina86.com> Cc: Marek Szyprowski <m.szyprowski@samsung.com> Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com> Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> Cc: Catalin Marinas <catalin.marinas@arm.com> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
dee2f8aaab
commit
620951e274
6
mm/cma.c
6
mm/cma.c
@ -33,6 +33,7 @@
|
||||
#include <linux/log2.h>
|
||||
#include <linux/cma.h>
|
||||
#include <linux/highmem.h>
|
||||
#include <linux/io.h>
|
||||
|
||||
struct cma {
|
||||
unsigned long base_pfn;
|
||||
@ -324,6 +325,11 @@ int __init cma_declare_contiguous(phys_addr_t base,
|
||||
}
|
||||
}
|
||||
|
||||
/*
|
||||
* kmemleak scans/reads tracked objects for pointers to other
|
||||
* objects but this address isn't mapped and accessible
|
||||
*/
|
||||
kmemleak_ignore(phys_to_virt(addr));
|
||||
base = addr;
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user