All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Vernon <mcv21@cam.ac.uk>
To: Ian Campbell <ian.campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: Memory leak in migration on Xen 4.4
Date: Fri, 20 Nov 2015 15:22:57 +0000	[thread overview]
Message-ID: <564F3AD1.5030205@cam.ac.uk> (raw)
In-Reply-To: <1447944676.5647.77.camel@citrix.com>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

Hello,

On 19/11/15 14:51, Ian Campbell wrote:
> Following on from IRC conversation regarding an issue similar to [0] (which
> was reported by someone else).
> 
> I've implemented the missing hypercall support in valgrind, see attached
> which applies to SVN r15732. This is migrating cleanly (i.e. no
> "README_MISSING_SYSCALL_OR_IOCTL" spew) for me with the attached
> suppression file which knocks out one known (benign) issue.

I applied this patch to unstable's valgrind, and have now performed a
migration in both directions (see attached).

> With this things appear pretty clean using the Jessie packages for
> everything. Just a few k lost or remaining reachable at the end (see
> attached logs).

Can I suggest you try the kernel from jessie-backports? That's what I'm
using; I have kernel 4.2.0 (I needed this because 3.6 from jessie
doesn't support some of my hardware when running Xen).

This is a 1G guest again, and you'll see that receiving version gets
through over 4G.

Regards,

Matthew


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: xsl_receive.log --]
[-- Type: text/x-log; name="xsl_receive.log", Size: 3550 bytes --]

==17035== Memcheck, a memory error detector
==17035== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==17035== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==17035== Command: /usr/lib/xen-4.4/bin/libxl-save-helper.orig --restore-domain 6 9 1 0 2 0 0 1 0 1 0 0
==17035== Parent PID: 17034
==17035== 
==17035== Warning: set address range perms: large range [0x395dc040, 0x795dc040) (defined)
==17035== Warning: set address range perms: large range [0x795dd040, 0xb95dd040) (defined)
==17035== Warning: set address range perms: large range [0xb95de040, 0xf93de040) (undefined)
==17035== Warning: set address range perms: large range [0xf93df000, 0x1393df000) (defined)
==17035== Warning: set address range perms: large range [0xf93df000, 0x1393df000) (noaccess)
==17035== Warning: set address range perms: large range [0x395dc028, 0x795dc058) (noaccess)
==17035== Warning: set address range perms: large range [0x795dd028, 0xb95dd058) (noaccess)
==17035== Warning: set address range perms: large range [0xb95de028, 0xf93de058) (noaccess)
==17035== 
==17035== HEAP SUMMARY:
==17035==     in use at exit: 2,098,392 bytes in 4 blocks
==17035==   total heap usage: 2,822 allocs, 2,818 frees, 4,342,797,896 bytes allocated
==17035== 
==17035== 8 bytes in 1 blocks are definitely lost in loss record 1 of 4
==17035==    at 0x4C28CA0: malloc (vg_replace_malloc.c:299)
==17035==    by 0x4C2B04F: realloc (vg_replace_malloc.c:785)
==17035==    by 0x5064405: ??? (in /usr/lib/x86_64-linux-gnu/libxenguest-4.4.so)
==17035==    by 0x5063E02: ??? (in /usr/lib/x86_64-linux-gnu/libxenguest-4.4.so)
==17035==    by 0x5065ADB: xc_domain_restore (in /usr/lib/x86_64-linux-gnu/libxenguest-4.4.so)
==17035==    by 0x4014AF: ??? (in /usr/lib/xen-4.4/bin/libxl-save-helper.orig)
==17035==    by 0x54C6B44: (below main) (libc-start.c:287)
==17035== 
==17035== 24 bytes in 1 blocks are still reachable in loss record 2 of 4
==17035==    at 0x4C28CA0: malloc (vg_replace_malloc.c:299)
==17035==    by 0x401774: ??? (in /usr/lib/xen-4.4/bin/libxl-save-helper.orig)
==17035==    by 0x401456: ??? (in /usr/lib/xen-4.4/bin/libxl-save-helper.orig)
==17035==    by 0x54C6B44: (below main) (libc-start.c:287)
==17035== 
==17035== 1,208 bytes in 1 blocks are still reachable in loss record 3 of 4
==17035==    at 0x4C28CA0: malloc (vg_replace_malloc.c:299)
==17035==    by 0x4E4A08A: ??? (in /usr/lib/x86_64-linux-gnu/libxenctrl-4.4.so)
==17035==    by 0x4017CC: ??? (in /usr/lib/xen-4.4/bin/libxl-save-helper.orig)
==17035==    by 0x401456: ??? (in /usr/lib/xen-4.4/bin/libxl-save-helper.orig)
==17035==    by 0x54C6B44: (below main) (libc-start.c:287)
==17035== 
==17035== 2,097,152 bytes in 1 blocks are definitely lost in loss record 4 of 4
==17035==    at 0x4C28CA0: malloc (vg_replace_malloc.c:299)
==17035==    by 0x5065806: xc_domain_restore (in /usr/lib/x86_64-linux-gnu/libxenguest-4.4.so)
==17035==    by 0x4014AF: ??? (in /usr/lib/xen-4.4/bin/libxl-save-helper.orig)
==17035==    by 0x54C6B44: (below main) (libc-start.c:287)
==17035== 
==17035== LEAK SUMMARY:
==17035==    definitely lost: 2,097,160 bytes in 2 blocks
==17035==    indirectly lost: 0 bytes in 0 blocks
==17035==      possibly lost: 0 bytes in 0 blocks
==17035==    still reachable: 1,232 bytes in 2 blocks
==17035==         suppressed: 0 bytes in 0 blocks
==17035== 
==17035== For counts of detected and suppressed errors, rerun with: -v
==17035== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: xsl_send.log --]
[-- Type: text/x-log; name="xsl_send.log", Size: 2114 bytes --]

==6331== Memcheck, a memory error detector
==6331== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==6331== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==6331== Command: /usr/lib/xen-4.4/bin/libxl-save-helper.orig --save-domain 8 9 0 0 1 0 0 12 8 72
==6331== Parent PID: 6330
==6331== 
==6331== Warning: set address range perms: large range [0xa292000, 0x2a692000) (defined)
==6331== Warning: set address range perms: large range [0x395dc000, 0x795dc000) (defined)
==6331== Warning: set address range perms: large range [0x395dc000, 0x795dc000) (noaccess)
==6331== Warning: set address range perms: large range [0xa292000, 0x2a692000) (noaccess)
==6331== 
==6331== HEAP SUMMARY:
==6331==     in use at exit: 1,232 bytes in 2 blocks
==6331==   total heap usage: 697 allocs, 695 frees, 38,370,651 bytes allocated
==6331== 
==6331== 24 bytes in 1 blocks are still reachable in loss record 1 of 2
==6331==    at 0x4C28CA0: malloc (vg_replace_malloc.c:299)
==6331==    by 0x401774: ??? (in /usr/lib/xen-4.4/bin/libxl-save-helper.orig)
==6331==    by 0x40128C: ??? (in /usr/lib/xen-4.4/bin/libxl-save-helper.orig)
==6331==    by 0x54C6B44: (below main) (libc-start.c:287)
==6331== 
==6331== 1,208 bytes in 1 blocks are still reachable in loss record 2 of 2
==6331==    at 0x4C28CA0: malloc (vg_replace_malloc.c:299)
==6331==    by 0x4E4A08A: ??? (in /usr/lib/x86_64-linux-gnu/libxenctrl-4.4.so)
==6331==    by 0x4017CC: ??? (in /usr/lib/xen-4.4/bin/libxl-save-helper.orig)
==6331==    by 0x40128C: ??? (in /usr/lib/xen-4.4/bin/libxl-save-helper.orig)
==6331==    by 0x54C6B44: (below main) (libc-start.c:287)
==6331== 
==6331== LEAK SUMMARY:
==6331==    definitely lost: 0 bytes in 0 blocks
==6331==    indirectly lost: 0 bytes in 0 blocks
==6331==      possibly lost: 0 bytes in 0 blocks
==6331==    still reachable: 1,232 bytes in 2 blocks
==6331==         suppressed: 0 bytes in 0 blocks
==6331== 
==6331== For counts of detected and suppressed errors, rerun with: -v
==6331== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)

[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2015-11-20 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 14:51 Memory leak in migration on Xen 4.4 Ian Campbell
2015-11-20 15:22 ` Matthew Vernon [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=564F3AD1.5030205@cam.ac.uk \
    --to=mcv21@cam.ac.uk \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xen.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 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.