Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • J jg-open
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
    • Locked Files
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • linux-arm
  • jg-open
  • Repository
Switch branch/tag
  • jg-open
  • mm
  • memblock.c
Find file BlameHistoryPermalink
  • Mike Rapoport's avatar
    memblock: exclude NOMAP regions from kmemleak · 6e44bd6d
    Mike Rapoport authored Oct 13, 2021
    Vladimir Zapolskiy reports:
    
    commit a7259df7 ("memblock: make memblock_find_in_range method private")
    invokes a kernel panic while running kmemleak on OF platforms with nomaped
    regions:
    
      Unable to handle kernel paging request at virtual address fff000021e00000
      [...]
        scan_block+0x64/0x170
        scan_gray_list+0xe8/0x17c
        kmemleak_scan+0x270/0x514
        kmemleak_write+0x34c/0x4ac
    
    Indeed, NOMAP regions don't have linear map entries so an attempt to scan
    these areas would fault.
    
    Prevent such faults by excluding NOMAP regions from kmemleak.
    
    Link: https://lore.kernel.org/all/8ade5174-b143-d621-8c8e-dc6a1898c6fb@linaro.org
    Fixes: a7259df7
    
     ("memblock: make memblock_find_in_range method private")
    Signed-off-by: default avatarMike Rapoport <rppt@linux.ibm.com>
    Tested-by: default avatarVladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
    6e44bd6d