The memleak tool shipped with bcc-tools fails to resolve driver/module symbols

Issue

• The memleak tool shipped with bcc-tools fails to resolve functions associated with modules and shows them as a part of the kernel itself:

  4096 bytes in 1 allocations from stack
              __alloc_pages_nodemask+0x279 [kernel]
              alloc_pages_vma+0xb5 [kernel]
              shmem_alloc_page+0x70 [kernel]
              shmem_getpage_gfp+0x451 [kernel]
              shmem_read_mapping_page_gfp+0x51 [kernel]
              i915_gem_object_get_pages_gtt+0x1f7 [kernel]  <--
              ____i915_gem_object_get_pages+0x22 [kernel]  <-- 
              __i915_gem_object_get_pages+0x60 [kernel]  <--
              i915_gem_set_domain_ioctl+0x28b [kernel]  <--
              drm_ioctl_kernel+0x6c [kernel] <--
              drm_ioctl+0x1e7 [kernel] <--
              do_vfs_ioctl+0x3a0 [kernel]
              sys_ioctl+0xa1 [kernel]
              system_call_fastpath+0x22 [kernel]
  

• These functions are actually associated with the below modules as per /proc/kallsyms:

  ffffffffc0359f80 t ____i915_gem_object_get_pages [i915]
  ffffffffc035bf10 t i915_gem_object_get_pages_gtt [i915]
  ffffffffc035e800 t i915_gem_set_domain_ioctl [i915]
  ffffffffc035c890 t __i915_gem_object_get_pages   [i915]
  ffffffffc023f460 T drm_ioctl [drm]
  ffffffffc023eec0 T drm_ioctl_kernel  [drm]