From: Li Zefan <lizf@cn.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Containers <containers@lists.linux-foundation.org>,
Paul Menage <menage@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cgroup: use read lock to guard find_existing_css_set()
Date: Thu, 24 Apr 2008 09:00:52 +0800 [thread overview]
Message-ID: <480FDBC4.9020001@cn.fujitsu.com> (raw)
In-Reply-To: <480EDBD2.2060709@linux.vnet.ibm.com>
Balbir Singh wrote:
> Li Zefan wrote:
>> The function does not modify anything (except the temporary
>> css template), so it's sufficient to hold read lock.
>>
>> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
>> ---
>> kernel/cgroup.c | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/kernel/cgroup.c b/kernel/cgroup.c
>> index 2727f92..e9eb5da 100644
>> --- a/kernel/cgroup.c
>> +++ b/kernel/cgroup.c
>> @@ -406,11 +406,11 @@ static struct css_set *find_css_set(
>>
>> /* First see if we already have a cgroup group that matches
>> * the desired set */
>> - write_lock(&css_set_lock);
>> + read_lock(&css_set_lock);
>> res = find_existing_css_set(oldcg, cgrp, template);
>> if (res)
>> get_css_set(res);
>> - write_unlock(&css_set_lock);
>> + read_unlock(&css_set_lock);
>>
>> if (res)
>> return res;
>
> Looks good to me. Did you run lockdep?
>
No, I found this when reading the code, but I do have done some test.
next prev parent reply other threads:[~2008-04-24 1:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 3:04 [PATCH] cgroup: use read lock to guard find_existing_css_set() Li Zefan
2008-04-23 6:48 ` Paul Menage
[not found] ` <480EA744.2050300-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-04-23 6:48 ` Paul Menage
2008-04-23 6:48 ` Balbir Singh
2008-04-23 6:48 ` Balbir Singh
[not found] ` <480EDBD2.2060709-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-04-24 1:00 ` Li Zefan
2008-04-24 1:00 ` Li Zefan [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-23 3:04 Li Zefan
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=480FDBC4.9020001@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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.