From: "Wouter M. Koolen" <W.M.Koolen-Wijkstra@cwi.nl>
To: "Wouter M. Koolen" <W.M.Koolen-Wijkstra@cwi.nl>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
x86@kernel.org, keithp@keithp.com
Subject: Re: kmemleak: unreferenced object in copy_thread
Date: Wed, 30 Nov 2011 20:06:38 +0000 [thread overview]
Message-ID: <4ED68CCE.1070400@cwi.nl> (raw)
In-Reply-To: <4ED68BBF.8010608@cwi.nl>
Add i915 maintainer Keith Packard to CC.
On 11/30/2011 08:02 PM, Wouter M. Koolen wrote:
>
> On 11/30/2011 11:54 AM, Catalin Marinas wrote:
>> I can't yet tell whether it's a false positive or not. Did the X
>> server die? Is the process with pid 1415 still around? The leaked
>> object looks like the thread stack (8K) and it should have been
>> removed when the corresponding process was killed.
> Hi Catalin,
>
> Just got lucky and hit it again. This time it occurred without
> killing. Here's the splat:
>
> unreferenced object 0xffff880003eda000 (size 8192):
> comm "Xorg", pid 1117, jiffies 4295143832 (age 34745.832s)
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 0f 00 00 00 0f 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<ffffffff813feeb1>] kmemleak_alloc+0x21/0x50
> [<ffffffff8111086b>] kmem_cache_alloc_trace+0xdb/0x1d0
> [<ffffffff81001fbe>] copy_thread+0x1be/0x260
> [<ffffffff81044953>] copy_process+0xee3/0x1520
> [<ffffffff810450d6>] do_fork+0x116/0x350
> [<ffffffff8100a7d3>] sys_clone+0x23/0x30
> [<ffffffff8141c173>] stub_clone+0x13/0x20
> [<ffffffffffffffff>] 0xffffffffffffffff
>
> The process 1117 is still alive. It is
>
> root 1117 2.1 1.3 147484 28152 tty7 Ss+ 09:55 13:02
> /usr/bin/X :0 vt7 -br -nolisten tcp -auth /var/run/xauth/A:0-Tdu4bb
>
>
> Actually, there now are several splats of a second kind, relating to
> i915 gem buffers (attached). This type of splat has been reported
> before in
> https://lkml.org/lkml/2011/10/4/15
> although that thread seems to be a dead end. Maybe these warnings have
> a common source?
>
> What would be a good next step?
>
> With kind regards,
>
> Wouter Koolen
prev parent reply other threads:[~2011-11-30 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 18:09 kmemleak: unreferenced object in copy_thread Wouter M. Koolen
2011-11-30 11:54 ` Catalin Marinas
2011-11-30 14:02 ` Wouter M. Koolen
2011-11-30 20:02 ` Wouter M. Koolen
2011-11-30 20:06 ` Wouter M. Koolen [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=4ED68CCE.1070400@cwi.nl \
--to=w.m.koolen-wijkstra@cwi.nl \
--cc=catalin.marinas@arm.com \
--cc=hpa@zytor.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox