From: Li Zefan <lizf.kern@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: dhowells@redhat.com, lizf@cn.fujitsu.com, paul.moore@hp.com,
johannes@sipsolutions.net, dipankar@in.ibm.com,
linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org, kvm@vger.kernel.org
Subject: Re: [PATCH 1/3] cgroup - removing superfluous rcu_read_lock_held check
Date: Wed, 03 Nov 2010 01:54:55 +0800 [thread overview]
Message-ID: <4CD0506F.6080600@gmail.com> (raw)
In-Reply-To: <1288638909-10541-2-git-send-email-jolsa@redhat.com>
On 2010年11月02日 03:15, Jiri Olsa wrote:
> hi,
This..
> the rcu_dereference_check is defined as
>
> #define rcu_dereference_check(p, c) \
> __rcu_dereference_check((p), rcu_read_lock_held() || (c), __rcu)
>
> so the caller does not need to specify rcu_read_lock_held() condition.
>
> wbr,
> jirka
and this should be excluded from the changelog.
>
>
> Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Reviewed-by: Li Zefan <lizf@cn.fujitsu.com>
However a nitpick:
> ---
> include/linux/cgroup.h | 1 -
> kernel/cgroup.c | 6 ++----
> 2 files changed, 2 insertions(+), 5 deletions(-)
...
> @@ -4544,7 +4542,7 @@ unsigned short css_id(struct cgroup_subsys_state *css)
> * it's unchanged until freed.
> */
> cssid = rcu_dereference_check(css->id,
> - rcu_read_lock_held() || atomic_read(&css->refcnt));
> + atomic_read(&css->refcnt));
Now the 2 lines can be made into one line and still fit into 80 chars.
>
> if (cssid)
> return cssid->id;
> @@ -4557,7 +4555,7 @@ unsigned short css_depth(struct cgroup_subsys_state *css)
> struct css_id *cssid;
>
> cssid = rcu_dereference_check(css->id,
> - rcu_read_lock_held() || atomic_read(&css->refcnt));
> + atomic_read(&css->refcnt));
dito
>
> if (cssid)
> return cssid->depth;
next prev parent reply other threads:[~2010-11-02 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 19:15 [PATCH 0/3] rcu - removing superfluous rcu_read_lock_held check Jiri Olsa
2010-11-01 19:15 ` [PATCH 1/3] cgroup " Jiri Olsa
2010-11-02 17:54 ` Li Zefan [this message]
2010-11-01 19:15 ` [PATCH 2/3] kernel,cred,kvm,security " Jiri Olsa
2010-11-01 22:42 ` Paolo Bonzini
2010-11-02 7:21 ` Jiri Olsa
2010-11-01 19:15 ` [PATCH 3/3] net " Jiri Olsa
2010-11-01 20:33 ` David Miller
2010-11-01 21:47 ` Paul Moore
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=4CD0506F.6080600@gmail.com \
--to=lizf.kern@gmail.com \
--cc=containers@lists.linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=johannes@sipsolutions.net \
--cc=jolsa@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=paul.moore@hp.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