From: Daniel Borkmann <dborkman@redhat.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: kmemleak through e1000?
Date: Tue, 04 Mar 2014 16:55:49 +0100 [thread overview]
Message-ID: <5315F785.4050602@redhat.com> (raw)
Hi all, I'm not very familiar with the e1000 code, but on the latest
net.git kernel I get reliably the following (not sure if it's actually
caused by e1000 though):
unreferenced object 0xffff8800361a7d80 (size 32):
comm "systemd-udevd", pid 246, jiffies 4294677997 (age 1117.522s)
hex dump (first 32 bytes):
60 7d 1a 36 00 88 ff ff 24 01 00 00 00 00 00 00 `}.6....$.......
f0 aa 35 81 ff ff ff ff 00 00 00 00 00 00 00 00 ..5.............
backtrace:
[<ffffffff8166609e>] kmemleak_alloc+0x4e/0xb0
[<ffffffff8119f547>] kmem_cache_alloc_trace+0xd7/0x220
[<ffffffff8135ad48>] populate_msi_sysfs+0x128/0x220
[<ffffffff8135b4b8>] pci_enable_msi_block+0x1b8/0x2c0
[<ffffffffa0221781>] e1000e_set_interrupt_capability+0x41/0x120 [e1000e]
[<ffffffffa0226047>] e1000_probe+0x3a7/0xe20 [e1000e]
[<ffffffff81343805>] local_pci_probe+0x45/0xa0
[<ffffffff81344b89>] pci_device_probe+0xd9/0x130
[<ffffffff813fc317>] driver_probe_device+0x87/0x390
[<ffffffff813fc6f3>] __driver_attach+0x93/0xa0
[<ffffffff813fa323>] bus_for_each_dev+0x63/0xa0
[<ffffffff813fbd6e>] driver_attach+0x1e/0x20
[<ffffffff813fb950>] bus_add_driver+0x180/0x250
[<ffffffff813fcd04>] driver_register+0x64/0xf0
[<ffffffff813431ab>] __pci_register_driver+0x4b/0x50
[<ffffffffa0240041>] iptable_filter_hook+0x41/0x70 [iptable_filter]
unreferenced object 0xffff8800c4ac1920 (size 32):
comm "NetworkManager", pid 409, jiffies 4294693366 (age 1102.161s)
hex dump (first 32 bytes):
34 34 00 c4 00 88 ff ff 00 00 00 00 00 00 00 00 44..............
00 00 00 00 00 00 00 00 6f 2e 32 00 00 00 00 00 ........o.2.....
backtrace:
[<ffffffff8166609e>] kmemleak_alloc+0x4e/0xb0
[<ffffffff8119f547>] kmem_cache_alloc_trace+0xd7/0x220
[<ffffffff8135ad2f>] populate_msi_sysfs+0x10f/0x220
[<ffffffff8135b4b8>] pci_enable_msi_block+0x1b8/0x2c0
[<ffffffffa0226ce5>] e1000_open+0x225/0x5b0 [e1000e]
[<ffffffff815785af>] __dev_open+0xbf/0x140
[<ffffffff815788bd>] __dev_change_flags+0x9d/0x170
[<ffffffff815789b9>] dev_change_flags+0x29/0x60
[<ffffffff81585482>] do_setlink+0x312/0x9e0
[<ffffffff81587958>] rtnl_newlink+0x508/0x710
[<ffffffff81584199>] rtnetlink_rcv_msg+0x99/0x260
[<ffffffff815a3269>] netlink_rcv_skb+0xa9/0xc0
[<ffffffff815840f8>] rtnetlink_rcv+0x28/0x30
[<ffffffff815a2bd8>] netlink_unicast+0x168/0x250
[<ffffffff815a2fa1>] netlink_sendmsg+0x2e1/0x3f0
[<ffffffff8155cc6b>] sock_sendmsg+0x8b/0xc0
unreferenced object 0xffff8800c4ac17a0 (size 32):
comm "NetworkManager", pid 409, jiffies 4294693366 (age 1102.161s)
hex dump (first 32 bytes):
20 19 ac c4 00 88 ff ff 24 01 00 00 00 00 00 00 .......$.......
f0 aa 35 81 ff ff ff ff 00 00 00 00 00 00 00 00 ..5.............
backtrace:
[<ffffffff8166609e>] kmemleak_alloc+0x4e/0xb0
[<ffffffff8119f547>] kmem_cache_alloc_trace+0xd7/0x220
[<ffffffff8135ad48>] populate_msi_sysfs+0x128/0x220
[<ffffffff8135b4b8>] pci_enable_msi_block+0x1b8/0x2c0
[<ffffffffa0226ce5>] e1000_open+0x225/0x5b0 [e1000e]
[<ffffffff815785af>] __dev_open+0xbf/0x140
[<ffffffff815788bd>] __dev_change_flags+0x9d/0x170
[<ffffffff815789b9>] dev_change_flags+0x29/0x60
[<ffffffff81585482>] do_setlink+0x312/0x9e0
[<ffffffff81587958>] rtnl_newlink+0x508/0x710
[<ffffffff81584199>] rtnetlink_rcv_msg+0x99/0x260
[<ffffffff815a3269>] netlink_rcv_skb+0xa9/0xc0
[<ffffffff815840f8>] rtnetlink_rcv+0x28/0x30
[<ffffffff815a2bd8>] netlink_unicast+0x168/0x250
[<ffffffff815a2fa1>] netlink_sendmsg+0x2e1/0x3f0
[<ffffffff8155cc6b>] sock_sendmsg+0x8b/0xc0
next reply other threads:[~2014-03-04 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 15:55 Daniel Borkmann [this message]
2014-03-04 20:58 ` kmemleak through e1000? Bjorn Helgaas
2014-03-04 21:11 ` [E1000-devel] " Nelson, Shannon
2014-03-04 21:33 ` Bjorn Helgaas
2014-03-04 21:55 ` Daniel Borkmann
2014-03-04 22:49 ` Bjorn Helgaas
2014-03-05 8:23 ` Daniel Borkmann
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=5315F785.4050602@redhat.com \
--to=dborkman@redhat.com \
--cc=bhelgaas@google.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-pci@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.