Re: [iovisor-dev] using BPF for driver memory leak detection

Yonghong Song

On Mon, Aug 6, 2018 at 2:44 AM, Krishna Chaitanya
<chaitanya.mgit@...> wrote:
On Mon, Aug 6, 2018 at 3:12 PM Krishna Chaitanya
<chaitanya.mgit@...> wrote:


If we want to use BPF for memory leak for driver modules, we can only
print outstanding allocations which could potentially be freed at a
later time.

Is there a simple way we could pre-load BPF (before driver insertion)
and check for the outstanding entries after the driver removal, which
are confirmed leaks?

This is useful to debug memory allocations at insmod/rmmod.

Currently, without insmod, BPF compilation fails as tracepoints are
not installed. And also if tracing is active, rmmod fails with
"resource in use".
Which tracepoint you tried to attach? For kernel memory, a few kmem
tracepoints are attached in memleak. If you want to attach a tracepoint
only defined by the module, yes, you may have to wait until the module
is inserted into the kernel.

+dev Migration Complete

Brendan OSullivan <bosullivan@...>

Greetings IO Visor  community!

We are writing to let you know that the migration of your mailing list services to is complete. Please be sure to visit to overview your current lists and settings. If you’d like to learn more about using , please reference their help documentation. If you need assistance with, please email helpdesk@... for The Linux Foundation’s helpdesk.