From: Alexandru Copot <alex.mihai.c@gmail.com>
To: rusty@rustcorp.com.au
Cc: Daniel Baluta <dbaluta@ixiacom.com>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, mst@redhat.com
Subject: [PATCH] virtio: suppress kmemleak false positive
Date: Fri, 18 Jan 2013 13:54:21 +0200 [thread overview]
Message-ID: <1358510061-12164-1-git-send-email-alex.mihai.c@gmail.com> (raw)
While doing simple IPv6 tests in KVM virtual machines,
(add an IPv6 address to eth0) kmemleak complains about
an unreferenced object:
unreferenced object 0xffff88001e804120 (size 32):
comm "softirq", pid 0, jiffies 4294900928 (age 631.544s)
hex dump (first 32 bytes):
28 cb fd 1d 00 00 00 00 0c 00 00 00 01 00 01 00 (...............
02 d0 83 1d 00 00 00 00 6e 00 00 00 00 00 00 00 ........n.......
backtrace:
[<ffffffff815ed721>] kmemleak_alloc+0x21/0x50
[<ffffffff8111d0b0>] __kmalloc+0xe0/0x160
[<ffffffff81362b7c>] virtqueue_add_buf+0x1fc/0x3d0
[<ffffffff8140cbd3>] start_xmit+0x153/0x3a0
[<ffffffff8150887e>] dev_hard_start_xmit+0x21e/0x470
[<ffffffff815247ce>] sch_direct_xmit+0xfe/0x280
[<ffffffff81509014>] dev_queue_xmit+0x1f4/0x5d0
[<ffffffff81592e91>] ip6_finish_output2+0x101/0x450
[<ffffffff81595ae8>] ip6_finish_output+0x98/0x200
[<ffffffff81595ca1>] ip6_output+0x51/0x1b0
[<ffffffff815b51af>] mld_sendpack+0x19f/0x360
[<ffffffff815b59b4>] mld_ifc_timer_expire+0x194/0x290
[<ffffffff8104b794>] call_timer_fn+0x74/0xf0
[<ffffffff8104bb1b>] run_timer_softirq+0x18b/0x220
[<ffffffff81045f81>] __do_softirq+0xe1/0x1c0
[<ffffffff8160a4fc>] call_softirq+0x1c/0x30
Seems the function vring_add_indirect stores an array of
struct vring_desc by using virt_to_phys and kmemleak
doesn't track the pointer.
The following patch can fix this.
Signed-off-by: Alexandru Copot <alex.mihai.c@gmail.com>
CC: Daniel Baluta <dbaluta@ixiacom.com>
---
drivers/virtio/virtio_ring.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
index ffd7e7d..730baa4 100644
--- a/drivers/virtio/virtio_ring.c
+++ b/drivers/virtio/virtio_ring.c
@@ -23,6 +23,7 @@
#include <linux/slab.h>
#include <linux/module.h>
#include <linux/hrtimer.h>
+#include <linux/kmemleak.h>
/* virtio guest is communicating with a virtual "device" that actually runs on
* a host processor. Memory barriers are used to control SMP effects. */
@@ -141,6 +142,11 @@ static int vring_add_indirect(struct vring_virtqueue *vq,
if (!desc)
return -ENOMEM;
+ /* This pointer is passed below by its physical address so
+ * kmemleak would show a false positive without it.
+ */
+ kmemleak_not_leak(desc);
+
/* Transfer entries from the sg list into the indirect page */
for (i = 0; i < out; i++) {
desc[i].flags = VRING_DESC_F_NEXT;
--
1.8.1
next reply other threads:[~2013-01-18 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 11:54 Alexandru Copot [this message]
[not found] <1357912303-17026-1-git-send-email-alex.mihai.c@gmail.com>
2013-01-11 14:02 ` [PATCH] virtio: suppress kmemleak false positive Catalin Marinas
[not found] ` <20130111140231.GA31281@arm.com>
2013-01-11 14:32 ` Daniel Baluta
2013-01-11 14:43 ` Daniel Baluta
2013-01-11 14:47 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2013-01-11 13:51 Alexandru Copot
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=1358510061-12164-1-git-send-email-alex.mihai.c@gmail.com \
--to=alex.mihai.c@gmail.com \
--cc=dbaluta@ixiacom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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).