From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Paul Menage <menage@google.com>,
Linux Containers <containers@lists.linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Serge Hallyn <serue@us.ibm.com>
Subject: [PATCHSET] fix CGROUP VS RCU
Date: Fri, 21 Nov 2008 16:49:13 +0800 [thread overview]
Message-ID: <49267609.8050600@cn.fujitsu.com> (raw)
current some cgroup struct are protected by RCU.
struct protected by RCU:
struct css_set, struct cgroup_subsys_state, struct cgroup
pointer protected by RCU:
struct task_struct.cgroups, struct css_set.subsys[*],
struct cgroup_subsys_state.cgroup
the last two pointers are readonly pointer!
these patches are fix these structs, and pointers. And a faker:
struct cgroup_subsys.root
Not cleanup all yet.
Thanx, Lai
next reply other threads:[~2008-11-21 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 8:49 Lai Jiangshan [this message]
2008-11-21 9:06 ` [PATCHSET] fix CGROUP VS RCU Andrew Morton
2008-11-21 9:10 ` Lai Jiangshan
2008-11-21 9:14 ` Lai Jiangshan
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=49267609.8050600@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=serue@us.ibm.com \
/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