From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Florian Westphal <fw@strlen.de>
Subject: Re: [Patch nf] nf_conntrack_extend: silent a memory leak warning
Date: Mon, 16 Apr 2018 17:44:04 +0200 [thread overview]
Message-ID: <20180416154404.eatjnxp25evbon4d@salvia> (raw)
In-Reply-To: <20180330202206.19565-1-xiyou.wangcong@gmail.com>
On Fri, Mar 30, 2018 at 01:22:06PM -0700, Cong Wang wrote:
> The following memory leak is false postive:
>
> unreferenced object 0xffff8f37f156fb38 (size 128):
> comm "softirq", pid 0, jiffies 4294899665 (age 11.292s)
> hex dump (first 32 bytes):
> 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
> 00 00 00 00 30 00 20 00 48 6b 6b 6b 6b 6b 6b 6b ....0. .Hkkkkkkk
> backtrace:
> [<000000004fda266a>] __kmalloc_track_caller+0x10d/0x141
> [<000000007b0a7e3c>] __krealloc+0x45/0x62
> [<00000000d08e0bfb>] nf_ct_ext_add+0xdc/0x133
> [<0000000099b47fd8>] init_conntrack+0x1b1/0x392
> [<0000000086dc36ec>] nf_conntrack_in+0x1ee/0x34b
> [<00000000940592de>] nf_hook_slow+0x36/0x95
> [<00000000d1bd4da7>] nf_hook.constprop.43+0x1c3/0x1dd
> [<00000000c3673266>] __ip_local_out+0xae/0xb4
> [<000000003e4192a6>] ip_local_out+0x17/0x33
> [<00000000b64356de>] igmp_ifc_timer_expire+0x23e/0x26f
> [<000000006a8f3032>] call_timer_fn+0x14c/0x2a5
> [<00000000650c1725>] __run_timers.part.34+0x150/0x182
> [<0000000090e6946e>] run_timer_softirq+0x2a/0x4c
> [<000000004d1e7293>] __do_softirq+0x1d1/0x3c2
> [<000000004643557d>] irq_exit+0x53/0xa2
> [<0000000029ddee8f>] smp_apic_timer_interrupt+0x22a/0x235
Applied, thanks.
prev parent reply other threads:[~2018-04-16 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 20:22 [Patch nf] nf_conntrack_extend: silent a memory leak warning Cong Wang
2018-04-16 15:44 ` 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=20180416154404.eatjnxp25evbon4d@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox