public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Ben Blum <bblum@andrew.cmu.edu>
Cc: Frederic Weisbecker <fweisbec@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Paul Menage <paul@paulmenage.org>,
	linux-kernel@vger.kernel.org
Subject: Re: BUG: cgroup_task_counter subsys may crash with whole-threadgroup move
Date: Mon, 17 Oct 2011 15:20:27 +0800	[thread overview]
Message-ID: <4E9BD73B.7060405@cn.fujitsu.com> (raw)
In-Reply-To: <20111014000913.GA22527@ghc17.ghc.andrew.cmu.edu>

08:09, Ben Blum wrote:
> I was testing some patches for cgroup_attach_proc and managed to cause a
> crash with the following usage pattern:
> 
>     mount -t cgroup none -o tasks /dev/cgroup
>     cd /dev/cgroup
>     mkdir foo
>     echo $PID > foo/cgroup.procs
>     echo $PID > tasks
>     echo $PID > foo/cgroup.procs
> 
> Where $PID is the thread ID of a member of a multithreaded process (my
> test program just does CLONE_THREAD 8 times and then all threads sleep).
> (It doesn't matter if the thread is the group leader or not, but a
> single-threaded process doesn't crash.)
> 
> And get the following kernel panic:
> http://maximegalon.andrew.cmu.edu/cgroup-taskstats/panic.txt
> 
> It's deterministic, and happens only when the "tasks" subsystem is
> mounted.
> 
> I'm using user-mode linux to test, with the following config:
> http://maximegalon.andrew.cmu.edu/cgroup-taskstats/config.txt
> 
> and I ran it in GDB to get the following backtrace:
> http://maximegalon.andrew.cmu.edu/cgroup-taskstats/bt.txt
> 

I've figured out what's wrong. Patch will be sent out soon.

Thanks for reporting this!

--
Li Zefan

      reply	other threads:[~2011-10-17  7:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14  0:09 BUG: cgroup_task_counter subsys may crash with whole-threadgroup move Ben Blum
2011-10-17  7:20 ` Li Zefan [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=4E9BD73B.7060405@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=bblum@andrew.cmu.edu \
    --cc=fweisbec@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=paul@paulmenage.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox