Re: V3.10-rc1 memory leak

2013-05-16 Thread Rusty Russell
Catalin Marinas writes: > On Wed, May 15, 2013 at 08:33:01PM +0100, Steven Rostedt wrote: >> On Wed, 2013-05-15 at 15:37 +0100, Catalin Marinas wrote: >> >> > >From 0621c7e1909ea86bf8499a0ffe5ea59d1007ee8c Mon Sep 17 00:00:00 2001 >> > From: Catalin Marinas >> > Date: Wed, 15 May 2013 15:30:46

Re: V3.10-rc1 memory leak

2013-05-16 Thread Catalin Marinas
On Wed, May 15, 2013 at 08:33:01PM +0100, Steven Rostedt wrote: > On Wed, 2013-05-15 at 15:37 +0100, Catalin Marinas wrote: > > > >From 0621c7e1909ea86bf8499a0ffe5ea59d1007ee8c Mon Sep 17 00:00:00 2001 > > From: Catalin Marinas > > Date: Wed, 15 May 2013 15:30:46 +0100 > > Subject: [PATCH] kmemle

Re: V3.10-rc1 memory leak

2013-05-15 Thread Larry Finger
On 05/15/2013 10:02 AM, Catalin Marinas wrote: On Wed, May 15, 2013 at 04:15:46AM +0100, Larry Finger wrote: I do not see that particular one; however, I see 4 instances of unreferenced object 0x8800b7979750 (size 8): comm "swapper/0", pid 1, jiffies 4294892402 (age 21888.316s) hex

Re: V3.10-rc1 memory leak

2013-05-15 Thread Steven Rostedt
On Wed, 2013-05-15 at 15:33 -0400, Steven Rostedt wrote: > Instead of just picking data sections by name (names that start > with .data, .bss or .ref.data), use the section flags and scan all > sections that are allocated, writable and not executable. Which should > cover all sections of a module

Re: V3.10-rc1 memory leak

2013-05-15 Thread Steven Rostedt
On Wed, 2013-05-15 at 15:37 +0100, Catalin Marinas wrote: > >From 0621c7e1909ea86bf8499a0ffe5ea59d1007ee8c Mon Sep 17 00:00:00 2001 > From: Catalin Marinas > Date: Wed, 15 May 2013 15:30:46 +0100 > Subject: [PATCH] kmemleak: Scan the jump label module section > > Objects allocated in jump_label_

Re: V3.10-rc1 memory leak

2013-05-15 Thread Toshi Kani
On Wed, 2013-05-15 at 17:47 +0100, Catalin Marinas wrote: > On Wed, May 15, 2013 at 04:49:50PM +0100, Toshi Kani wrote: > > On Wed, 2013-05-15 at 16:02 +0100, Catalin Marinas wrote: > > > On Wed, May 15, 2013 at 04:15:46AM +0100, Larry Finger wrote: > > > > I do not see that particular one; however

Re: V3.10-rc1 memory leak

2013-05-15 Thread Catalin Marinas
On Wed, May 15, 2013 at 04:49:50PM +0100, Toshi Kani wrote: > On Wed, 2013-05-15 at 16:02 +0100, Catalin Marinas wrote: > > On Wed, May 15, 2013 at 04:15:46AM +0100, Larry Finger wrote: > > > I do not see that particular one; however, I see 4 instances of > > > > > > unreferenced object 0x8800

Re: V3.10-rc1 memory leak

2013-05-15 Thread Toshi Kani
On Wed, 2013-05-15 at 16:02 +0100, Catalin Marinas wrote: > On Wed, May 15, 2013 at 04:15:46AM +0100, Larry Finger wrote: > > I do not see that particular one; however, I see 4 instances of > > > > unreferenced object 0x8800b7979750 (size 8): > >comm "swapper/0", pid 1, jiffies 4294892402

Re: V3.10-rc1 memory leak

2013-05-15 Thread Catalin Marinas
On Wed, May 15, 2013 at 04:15:46AM +0100, Larry Finger wrote: > I do not see that particular one; however, I see 4 instances of > > unreferenced object 0x8800b7979750 (size 8): >comm "swapper/0", pid 1, jiffies 4294892402 (age 21888.316s) >hex dump (first 8 bytes): > 31 38 00 b7 0

Re: V3.10-rc1 memory leak

2013-05-15 Thread Catalin Marinas
On Wed, May 15, 2013 at 01:57:03AM +0100, Steven Rostedt wrote: > On Tue, 2013-05-14 at 17:20 -0400, Steven Rostedt wrote: > > On Tue, 2013-05-14 at 16:10 -0500, Larry Finger wrote: > > > On 05/14/2013 03:30 PM, Catalin Marinas wrote: > > > > > > > > I just got a patch today: > > > > > > > > https:

Re: V3.10-rc1 memory leak

2013-05-14 Thread Larry Finger
On 05/14/2013 07:57 PM, Steven Rostedt wrote: On Tue, 2013-05-14 at 17:20 -0400, Steven Rostedt wrote: On Tue, 2013-05-14 at 16:10 -0500, Larry Finger wrote: On 05/14/2013 03:30 PM, Catalin Marinas wrote: I just got a patch today: https://lkml.org/lkml/2013/5/10/607 which could be related.

Re: V3.10-rc1 memory leak

2013-05-14 Thread Steven Rostedt
On Tue, 2013-05-14 at 17:20 -0400, Steven Rostedt wrote: > On Tue, 2013-05-14 at 16:10 -0500, Larry Finger wrote: > > On 05/14/2013 03:30 PM, Catalin Marinas wrote: > > > > > > I just got a patch today: > > > > > > https://lkml.org/lkml/2013/5/10/607 > > > > > > which could be related. If Rusty doe

Re: V3.10-rc1 memory leak

2013-05-14 Thread Steven Rostedt
On Tue, 2013-05-14 at 16:10 -0500, Larry Finger wrote: > On 05/14/2013 03:30 PM, Catalin Marinas wrote: > > > > I just got a patch today: > > > > https://lkml.org/lkml/2013/5/10/607 > > > > which could be related. If Rusty doesn't push it I'll do. But please let > > me know if it does not solve the

Re: V3.10-rc1 memory leak

2013-05-14 Thread Larry Finger
On 05/14/2013 03:30 PM, Catalin Marinas wrote: I just got a patch today: https://lkml.org/lkml/2013/5/10/607 which could be related. If Rusty doesn't push it I'll do. But please let me know if it does not solve the problem. This patch fixes my problem. Now I can see the next new problem repo

Re: V3.10-rc1 memory leak

2013-05-14 Thread Larry Finger
On 05/14/2013 02:09 PM, Steven Rostedt wrote: On Mon, 2013-05-13 at 15:06 -0400, Larry Finger wrote: Using v3.10-rc1-68-g2d3ec09, I am getting many instances of the following from kmemleak: unreferenced object 0x8800b546dc30 (size 48): comm "systemd-udevd", pid 2181, jiffies 4294899141

Re: V3.10-rc1 memory leak

2013-05-14 Thread Catalin Marinas
Hi Steve, On Tue, May 14, 2013 at 08:09:46PM +0100, Steven Rostedt wrote: > # find /debug/tracing/events/ -name format |xargs grep 8800769f7438 > /debug/tracing/events/drm/drm_vblank_event_delivered/format: field:pid_t > pid;offset:8; size:4; signed:1;8800769f7438 > > Thus

Re: V3.10-rc1 memory leak

2013-05-14 Thread Steven Rostedt
On Mon, 2013-05-13 at 15:06 -0400, Larry Finger wrote: > Using v3.10-rc1-68-g2d3ec09, I am getting many instances of the following > from > kmemleak: > > unreferenced object 0x8800b546dc30 (size 48): >comm "systemd-udevd", pid 2181, jiffies 4294899141 (age 274.096s) >hex dump (first

V3.10-rc1 memory leak

2013-05-13 Thread Larry Finger
Using v3.10-rc1-68-g2d3ec09, I am getting many instances of the following from kmemleak: unreferenced object 0x8800b546dc30 (size 48): comm "systemd-udevd", pid 2181, jiffies 4294899141 (age 274.096s) hex dump (first 32 bytes): 00 dc 46 b5 00 88 ff ff d0 ff 5b a0 ff ff ff ff ..F