linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Vagin <avagin@gmail.com>
To: Kirill Tkhai <ktkhai@virtuozzo.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Mount structures are leaked
Date: Thu, 8 Jun 2017 13:49:38 -0700	[thread overview]
Message-ID: <CANaxB-zOEPpZ4ohYkpb1-36OMsD+8VH6HP_6GP_suSe_AF150Q@mail.gmail.com> (raw)

Hello,

We found that mount structures are leaked on the upstream linux kernel:

[root@zdtm criu]# cat /proc/slabinfo | grep mnt
mnt_cache          36456  36456    384   42    4 : tunables    0    0
  0 : slabdata    868    868      0
[root@zdtm criu]#  python test/zdtm.py run  -t zdtm/static/env00
--iter 10 -f ns
=== Run 1/1 ================ zdtm/static/env00

========================= Run zdtm/static/env00 in ns ==========================
Start test
./env00 --pidfile=env00.pid --outfile=env00.out --envname=ENV_00_TEST
Run criu dump
Run criu restore
Run criu dump
....
Run criu restore
Send the 15 signal to  339
Wait for zdtm/static/env00(339) to die for 0.100000
Removing dump/zdtm/static/env00/31
========================= Test zdtm/static/env00 PASS ==========================
[root@zdtm criu]# cat /proc/slabinfo | grep mnt
mnt_cache          36834  36834    384   42    4 : tunables    0    0
  0 : slabdata    877    877      0

[root@zdtm linux]# git describe HEAD
v4.12-rc4-122-gb29794e

[root@zdtm ~]# uname -a
Linux zdtm.openvz.org 4.12.0-rc4+ #2 SMP Thu Jun 8 20:49:01 CEST 2017
x86_64 x86_64 x86_64 GNU/Linux

Thanks,
Andrei

             reply	other threads:[~2017-06-08 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 20:49 Andrei Vagin [this message]
2017-06-08 21:37 ` Mount structures are leaked Al Viro
2017-06-08 22:48   ` Andrei Vagin
2017-06-09  2:13     ` Andrei Vagin

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=CANaxB-zOEPpZ4ohYkpb1-36OMsD+8VH6HP_6GP_suSe_AF150Q@mail.gmail.com \
    --to=avagin@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=ktkhai@virtuozzo.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).