All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Sagi Grimberg <sagi@grimberg.me>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: kmemleak complaints on request queue stats (virtio)
Date: Wed, 29 Mar 2017 11:04:07 -0600	[thread overview]
Message-ID: <401a0b33-c8ea-d71d-7a9e-3dc47c9129ef@kernel.dk> (raw)
In-Reply-To: <c1659bc3-82e1-7d05-cec7-d5a6e78bd8e5@grimberg.me>

On 03/29/2017 11:02 AM, Sagi Grimberg wrote:
> Hi,
> 
> I just got the below kmemleak report. Just thought I'd send it
> out as I don't have time to look into it just now...
> 
> --
> unreferenced object 0xffff8ab236717920 (size 32):
>    comm "swapper/0", pid 1, jiffies 4294892551 (age 9966.044s)
>    hex dump (first 32 bytes):
>      20 79 71 36 b2 8a ff ff 20 79 71 36 b2 8a ff ff   yq6.... yq6....
>      00 00 00 00 ff ff ff ff e0 c1 4b 9b ff ff ff ff  ..........K.....
>    backtrace:
>      [<ffffffff9b84212a>] kmemleak_alloc+0x4a/0xa0
>      [<ffffffff9b1ff780>] kmem_cache_alloc_trace+0x110/0x230
>      [<ffffffff9b3cd74f>] blk_alloc_queue_stats+0x1f/0x40
>      [<ffffffff9b3bacd4>] blk_alloc_queue_node+0x94/0x2e0
>      [<ffffffff9b3cbdd0>] blk_mq_init_queue+0x20/0x60
>      [<ffffffff9b593665>] loop_add+0xe5/0x270
>      [<ffffffff9bfe348b>] loop_init+0x10b/0x149
>      [<ffffffff9b002193>] do_one_initcall+0x53/0x1a0
>      [<ffffffff9bf8b133>] kernel_init_freeable+0x16d/0x1f3
>      [<ffffffff9b83ed0e>] kernel_init+0xe/0x100
>      [<ffffffff9b84d27c>] ret_from_fork+0x2c/0x40
>      [<ffffffffffffffff>] 0xffffffffffffffff

You don't mention what you are running? But I'm assuming it was my 4.12
branch. If so, this is fixed in a later revision of it.  If you pull an
update, it should go away.

-- 
Jens Axboe

  reply	other threads:[~2017-03-29 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 17:02 kmemleak complaints on request queue stats (virtio) Sagi Grimberg
2017-03-29 17:04 ` Jens Axboe [this message]
2017-03-29 17:06   ` Sagi Grimberg

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=401a0b33-c8ea-d71d-7a9e-3dc47c9129ef@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=sagi@grimberg.me \
    /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.