On Mon, Aug 6, 2018 at 2:44 AM, Krishna Chaitanya <[email protected]> wrote: > On Mon, Aug 6, 2018 at 3:12 PM Krishna Chaitanya > <[email protected]> wrote: >> >> Hi, >> >> 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 > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2): https://lists.iovisor.org/g/main/message/2 Mute This Topic: https://lists.iovisor.org/mt/24211362/21656 Group Owner: [email protected] Unsubscribe: https://lists.iovisor.org/g/main/leave/2589919/776971353/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
