mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Hills <mark@pogo.org.uk>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
	linux-kernel@vger.kernel.org, balbir@linux.vnet.ibm.com
Subject: Re: cgroup: rmdir() does not complete
Date: Wed, 1 Sep 2010 12:10:23 +0100 (BST)	[thread overview]
Message-ID: <alpine.NEB.2.01.1009011200050.6596@jrf.vwaro.pbz> (raw)
In-Reply-To: <20100827144225.3190167a.kamezawa.hiroyu@jp.fujitsu.com>

On Fri, 27 Aug 2010, KAMEZAWA Hiroyuki wrote:

> On Fri, 27 Aug 2010 12:39:48 +0900
> Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> 
> > On Fri, 27 Aug 2010 11:35:06 +0900
> > KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > 
> > > On Fri, 27 Aug 2010 09:56:39 +0900
> > > Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> > > 
> > > > > Or is it likely to be some other cause, and how best to find it?
> > > > > 
> > > > What cgroup subsystem did you mount where the directory existed you tried
> > > > to rmdir() first ?
> > > > If you mounted several subsystems on the same hierarchy, can you mount them
> > > > separately to narrow down the cause ?
> > > > 
> > > 
> > > It seems I can reproduce the issue on mmotm-0811, too.
> > > 
> > > try this.
> > > 
> > > Here, memory cgroup is mounted at /cgroups.
> > > ==
> > > #!/bin/bash -x
> > > 
> > > while sleep 1; do
> > >         date
> > >         mkdir /cgroups/test
> > >         echo 0 > /cgroups/test/tasks
> > >         echo 300M > /cgroups/test/memory.limit_in_bytes
> > >         cat /proc/self/cgroup
> > >         dd if=/dev/zero of=./tmpfile bs=4096 count=100000
> > >         echo 0 > /cgroups/tasks
> > >         cat /proc/self/cgroup
> > >         rmdir /cgroups/test
> > >         rm ./tmpfile
> > > done
> > > ==
> > > 
> > > hangs at rmdir. I'm no investigating force_empty.
> > > 
> > Thank you very much for your information.
> > 
> > Some questions.
> > 
> > Is "tmpfile" created on a normal filesystem(e.g. ext3) or tmpfs ?
> on ext4.
> 
> > And, how long does it likely to take to cause this problem ?
> 
> very soon. 10-20 loop.

I repeated the test above, but did not see a problem after many hundreds 
of loops.

My test was with the same kernel from my original bug report (Fedora 
2.6.33.6-147), using memory cgroup only and ext4 filesystem.

So it is possible we are experiencing different bugs with similar 
symptoms.

-- 
Mark

  parent reply	other threads:[~2010-09-01 11:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26 15:51 Mark Hills
2010-08-27  0:56 ` Daisuke Nishimura
2010-08-27  1:20   ` Balbir Singh
2010-08-27  2:35   ` KAMEZAWA Hiroyuki
2010-08-27  3:39     ` Daisuke Nishimura
2010-08-27  5:42       ` KAMEZAWA Hiroyuki
2010-08-27  6:29         ` KAMEZAWA Hiroyuki
2010-08-30  7:32           ` Balbir Singh
2010-08-30  9:13         ` Mark Hills
2010-09-01 11:10         ` Mark Hills [this message]
2010-09-01 23:42           ` KAMEZAWA Hiroyuki
2010-09-02  9:45             ` Mark Hills
2010-09-09 10:01             ` Mark Hills
2010-09-09 10:09               ` Balbir Singh
2010-09-09 11:36                 ` Mark Hills
2010-09-09 11:50                   ` Peter Zijlstra
2010-09-09 23:04                     ` Mark Hills
2010-09-09 23:43                       ` KAMEZAWA Hiroyuki
2010-09-10  2:16                       ` KAMEZAWA Hiroyuki
2010-09-10  4:05                         ` Daisuke Nishimura
2010-09-10  4:11                           ` KAMEZAWA Hiroyuki
2010-09-10  7:28                         ` Mark Hills
2010-09-10  7:33                           ` KAMEZAWA Hiroyuki
2010-09-10  7:51                             ` Mark Hills
2010-08-27  1:25 ` KAMEZAWA Hiroyuki
2010-08-30  9:25   ` Mark Hills

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=alpine.NEB.2.01.1009011200050.6596@jrf.vwaro.pbz \
    --to=mark@pogo.org.uk \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nishimura@mxp.nes.nec.co.jp \
    /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

all inboxes | Powered by JetHome®