From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-users] unexpected Out Of Memory (OOM)
Date: Fri, 9 Aug 2013 08:53:49 -0400
Message-ID: <20130809125349.GD3580@phenom.dumpdata.com>
References: <1375833740.4843.50.camel@localhost>
	<1375864197.619.8.camel@kazak.uk.xensource.com>
	<1375865894.13572.7.camel@localhost>
	<1375868133.13572.13.camel@localhost>
	<1375870612.619.28.camel@kazak.uk.xensource.com>
	<1375874240.13572.23.camel@localhost>
	<1375882604.619.56.camel@kazak.uk.xensource.com>
	<1375885560.13572.28.camel@localhost>
	<1375911468.884.14.camel@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <1375911468.884.14.camel@localhost>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Olivier Bonvalet <xen.list@daevel.fr>
Cc: xen-users@lists.xen.org, Roger Pau Monne <roger.pau@citrix.com>, Ian Campbell <Ian.Campbell@citrix.com>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

> unreferenced object 0xffff88007cca8a80 (size 8):
>   comm "swapper/0", pid 1, jiffies 4294892300 (age 150.688s)
>   hex dump (first 8 bytes):
>     74 69 6d 65 72 31 00 a5                          timer1..
>   backtrace:
>     [<ffffffff811b70d6>] kasprintf+0x3e/0x40
>     [<ffffffff810e296d>] __kmalloc_track_caller+0xe7/0xf3
>     [<ffffffff811b7071>] kvasprintf+0x41/0x68
>     [<ffffffff811b70d6>] kasprintf+0x3e/0x40
>     [<ffffffff810056eb>] xen_setup_timer+0x62/0xc3
>     [<ffffffff8134296e>] xen_cpu_up+0x5b/0x367
>     [<ffffffff81348662>] _cpu_up+0xb8/0x124
>     [<ffffffff81348792>] cpu_up+0xc4/0xd0
... more of them.

Are all fixed in v3.11.