From: David Ahern <dsahern@gmail.com>
To: Paul Menzel <pmenzel+linux-netdev@molgen.mpg.de>,
"David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: kmemleak reports unreferenced object 0xf2bee080 (size 96)
Date: Thu, 7 Jun 2018 08:58:47 -0700 [thread overview]
Message-ID: <bdd72f43-c28d-4bfa-69f1-b0693732f9f6@gmail.com> (raw)
In-Reply-To: <5d7376e2-d936-38ed-3419-262fc64f6a40@molgen.mpg.de>
On 6/7/18 8:54 AM, Paul Menzel wrote:
> $ dmesg
> […]
> [ 677.139874] PM: suspend exit
> [ 678.490993] kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> [ 679.517022] r8169 0000:03:00.0 enp3s0: link up
> […]
> $ sudo more /sys/kernel/debug/kmemleak
> unreferenced object 0xf2bee080 (size 96):
> comm "systemd-network", pid 209, jiffies 4294894477 (age 851.812s)
> hex dump (first 32 bytes):
> 00 00 00 00 dc 05 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<fb9b1020>] kmem_cache_alloc_trace+0x195/0x3a0
> [<bbe5d9f4>] ip6_convert_metrics+0x4a/0xe0
> [<4d869f67>] ip6_route_info_create+0x294/0xd10
> [<2f08c8d0>] ip6_route_add+0x1d/0x90
> [<304de076>] inet6_rtm_newroute+0x72/0x80
> [<f9e280dd>] rtnetlink_rcv_msg+0x2df/0x4f0
> [<9287c3cf>] netlink_rcv_skb+0x8f/0x130
> [<fbddd35b>] rtnetlink_rcv+0x12/0x20
> [<60ffd06b>] netlink_unicast+0x1ab/0x2b0
> [<4260e680>] netlink_sendmsg+0x2b5/0x5c0
> [<ec0cda7b>] sock_sendmsg+0x5a/0xa0
> [<08adf1a5>] __sys_sendto+0xea/0x170
> [<93e4f4e1>] sys_socketcall+0x1f4/0x380
> [<dcd25cae>] do_fast_syscall_32+0xd3/0x360
> [<0ce0c28f>] entry_SYSENTER_32+0x4e/0x7c
> [<2324e043>] 0xffffffff
> ```
>
I'll take a look. Thanks for the report.
prev parent reply other threads:[~2018-06-07 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 15:54 kmemleak reports unreferenced object 0xf2bee080 (size 96) Paul Menzel
2018-06-07 15:58 ` David Ahern [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=bdd72f43-c28d-4bfa-69f1-b0693732f9f6@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmenzel+linux-netdev@molgen.mpg.de \
--cc=yoshfuji@linux-ipv6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).