From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Paul Menage <menage@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Containers <containers@lists.linux-foundation.org>,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [PATCH] cgroups: fix incorrect using rcu_dereference() in cgroup_subsys_state()
Date: Sat, 22 Nov 2008 11:22:31 +0800 [thread overview]
Message-ID: <49277AF7.3090000@cn.fujitsu.com> (raw)
In-Reply-To: <6599ad830811211007s43f0c683s9d56e0aed3af938@mail.gmail.com>
Paul Menage wrote:
> On Fri, Nov 21, 2008 at 12:49 AM, Lai Jiangshan <laijs@cn.fujitsu.com> wrote:
>> It's task->cgroups protected by RCU. and struct css_set.subsys[subsys_id]
>> is readonly(after init). so we don't need rcu_dereference() for
>> struct css_set.subsys[subsys_id].
>>
>> the ways using cgroup_subsys_state() safely:
>>
>> #1:
>> rcu_read_lock() / task_lock();
>> c = cgroup_subsys_state(tsk, id);
>> use c;
>> rcu_read_unlock() / task_unlock();
>
> You need to qualify that with the fact that if you're just using RCU,
> the subsys state may no longer be the state for the task that you're
> interested in, since we don't guarantee that the task won't move
> directly after you read the state pointer.
>
>>
>> #2: use cgroup_lock() for _current_ task.
>> cgroup_lock();
>> c = cgroup_subsys_state(current, id);
>> use c;
>> cgroup_unlock();
>
> No, if you use cgroup_lock() you can do this for any task.
> cgroup_lock() is the cgroups equivalent of the BKL, and definitely
> prevents all task movement between groups.
cgroup_exit() will defeat you.
>> static inline struct cgroup_subsys_state *task_subsys_state(
>> struct task_struct *task, int subsys_id)
>> {
>> - return rcu_dereference(task->cgroups->subsys[subsys_id]);
>> + /*
>> + * ->subsys[subsys_id] are read-only data, so we do not need
>> + * rcu_dereference() for it.
>> + */
>> + return rcu_dereference(task->cgroups)->subsys[subsys_id];
>> }
>
> Change looks OK but I think we can lose the additional comment.
>
> Paul
>
>
>
I just remembered I had deferred Li Zefan's patch.
(I'm also RCU developer, I had been writing CGROUP VS RCU then,
I thought these patches should be sent together, So I deferred his patch)
From: Li Zefan <lizf@cn.fujitsu.com>
Date: Mon, 25 Aug 2008 11:05:28 +0800
Subject: [PATCH] cgroup: fix wrong rcu_dereference()
It is tsk->cgroups which is protected by RCU.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
---
include/linux/cgroup.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
index c98dd7c..d911dc7 100644
--- a/include/linux/cgroup.h
+++ b/include/linux/cgroup.h
@@ -355,7 +355,7 @@ static inline struct cgroup_subsys_state *cgroup_subsys_state(
static inline struct cgroup_subsys_state *task_subsys_state(
struct task_struct *task, int subsys_id)
{
- return rcu_dereference(task->cgroups->subsys[subsys_id]);
+ return rcu_dereference(task->cgroups)->subsys[subsys_id];
}
static inline struct cgroup* task_cgroup(struct task_struct *task,
next prev parent reply other threads:[~2008-11-22 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 8:49 [PATCH] cgroups: fix incorrect using rcu_dereference() in cgroup_subsys_state() Lai Jiangshan
2008-11-21 18:07 ` Paul Menage
[not found] ` <6599ad830811211007s43f0c683s9d56e0aed3af938-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-22 3:22 ` Lai Jiangshan
2008-11-22 3:22 ` Lai Jiangshan [this message]
2008-11-24 20:45 ` Paul Menage
[not found] ` <49277AF7.3090000-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-11-24 20:45 ` Paul Menage
[not found] ` <4926761E.8030002-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-11-21 18:07 ` Paul Menage
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 8:49 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=49277AF7.3090000@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.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 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.