From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: wireless_send_event kmemleaks
Date: Tue, 01 Sep 2009 14:43:05 -0400 [thread overview]
Message-ID: <1251830585.14862.2.camel@mj> (raw)
In-Reply-To: <43e72e890909011024p7b7176a6vfad3902ac714df79@mail.gmail.com>
On Tue, 2009-09-01 at 10:24 -0700, Luis R. Rodriguez wrote:
> Can't tell you how to reproduce yet.
>
> unreferenced object 0xffff88003ba5fd00 (size 256):
> comm "events/0", pid 9, jiffies 4297130623
> backtrace:
> [<ffffffff8112200d>] create_object+0x13d/0x2d0
> [<ffffffff811222c5>] kmemleak_alloc+0x25/0x60
> [<ffffffff81118a63>] kmem_cache_alloc_node+0x193/0x200
> [<ffffffff81446cca>] __alloc_skb+0x4a/0x180
> [<ffffffff81506be2>] wireless_send_event+0x1f2/0x410
I wonder if we can translate it to the line numbers. Together with the
git revision, it would be quite useful. addr2line can do it for an
individual address, but to process the whole dump, a script would be
needed.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2009-09-01 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 17:24 wireless_send_event kmemleaks Luis R. Rodriguez
2009-09-01 18:43 ` Pavel Roskin [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=1251830585.14862.2.camel@mj \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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;
as well as URLs for NNTP newsgroup(s).