From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Shyam Saini <mayhs11saini@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] examples: Fix memory leaks detected by Valgrind
Date: Mon, 4 Sep 2017 22:49:47 +0200 [thread overview]
Message-ID: <20170904204947.GA14775@salvia> (raw)
In-Reply-To: <1504010976-13897-1-git-send-email-mayhs11saini@gmail.com>
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.
prev parent reply other threads:[~2017-09-04 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 12:49 [PATCH] examples: Fix memory leaks detected by Valgrind Shyam Saini
2017-08-29 21:39 ` Arturo Borrero Gonzalez
2017-08-30 7:18 ` Shyam Saini
2017-09-04 20:49 ` Pablo Neira Ayuso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170904204947.GA14775@salvia \
--to=pablo@netfilter.org \
--cc=mayhs11saini@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.