On Tue, Aug 29, 2017 at 06:19:36PM +0530, Shyam Saini wrote: > ==11688== HEAP SUMMARY: > ==11688== in use at exit: 40 bytes in 1 blocks > ==11688== total heap usage: 7 allocs, 6 frees, 220 bytes allocated > ==11688== > ==11688== 40 bytes in 1 blocks are definitely lost in loss record 1 of 1 > ==11688== at 0x4C2AB80: malloc (in > /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) > ==11688== by 0x5068955: mnl_nlmsg_batch_start (nlmsg.c:441) > ==11688== by 0x40133B: main (nft-chain-add.c:103) > ==11688== > ==11688== LEAK SUMMARY: > ==11688== definitely lost: 40 bytes in 1 blocks > ==11688== indirectly lost: 0 bytes in 0 blocks > ==11688== possibly lost: 0 bytes in 0 blocks > ==11688== still reachable: 0 bytes in 0 blocks > ==11688== suppressed: 0 bytes in 0 blocks > > ==11831== HEAP SUMMARY: > ==11831== in use at exit: 40 bytes in 1 blocks > ==11831== total heap usage: 7 allocs, 6 frees, 220 bytes allocated > ==11831== > ==11831== 40 bytes in 1 blocks are definitely lost in loss record 1 of 1 > ==11831== at 0x4C2AB80: malloc (in > /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) > ==11831== by 0x5068955: mnl_nlmsg_batch_start (nlmsg.c:441) > ==11831== by 0x401154: main (nft-chain-del.c:79) > ==11831== > ==11831== LEAK SUMMARY: > ==11831== definitely lost: 40 bytes in 1 blocks > ==11831== indirectly lost: 0 bytes in 0 blocks > ==11831== possibly lost: 0 bytes in 0 blocks > ==11831== still reachable: 0 bytes in 0 blocks > ==11831== suppressed: 0 bytes in 0 blocks Applied, thanks. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
