From: David Miller <davem@davemloft.net>
To: lizf@cn.fujitsu.com
Cc: herbert@gondor.hengli.com.au, davej@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
peterz@infradead.org, menage@google.com
Subject: Re: [PATCH v2] cls_cgroup: Fix rcu lockdep warning
Date: Fri, 03 Sep 2010 09:55:39 -0700 (PDT) [thread overview]
Message-ID: <20100903.095539.220051635.davem@davemloft.net> (raw)
In-Reply-To: <4C805293.1020305@cn.fujitsu.com>
From: Li Zefan <lizf@cn.fujitsu.com>
Date: Fri, 03 Sep 2010 09:42:43 +0800
> Dave reported an rcu lockdep warning on 2.6.35.4 kernel
>
> task->cgroups and task->cgroups->subsys[i] are protected by RCU.
> So we avoid accessing invalid pointers here. This might happen,
> for example, when you are deref-ing those pointers while someone
> move @task from one cgroup to another.
>
> Reported-by: Dave Jones <davej@redhat.com>
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
Applied, thanks.
prev parent reply other threads:[~2010-09-03 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 1:42 [PATCH v2] cls_cgroup: Fix rcu lockdep warning Li Zefan
2010-09-03 16:55 ` David Miller [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=20100903.095539.220051635.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davej@redhat.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).