On 10.04.19 г. 9:34 ч., Qu Wenruo wrote: > Hi, > > As we have memleak.py in bcc tools, and it provides better info > including the calling stack, I'm wondering if we should replace current > eb leakage check with bcc based one. > > Any idea on this? Why do you want to change it, given that the existing one is only activate if btrfs is compiled with debug enabled and is "seamless"? What are we going to gain by introducing yet another tool or replacing an existing infrastructure with bcc (or whatever) based one? > > Thanks, > Qu >
