From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752182Ab0IBKiv (ORCPT ); Thu, 2 Sep 2010 06:38:51 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:51376 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751022Ab0IBKiu convert rfc822-to-8bit (ORCPT ); Thu, 2 Sep 2010 06:38:50 -0400 Subject: Re: [PATCH] cls_cgroup: Fix rcu lockdep warning From: Peter Zijlstra To: Li Zefan Cc: David Miller , Herbert Xu , Dave Jones , netdev , LKML , "Paul E. McKenney" In-Reply-To: <4C7F446F.8040303@cn.fujitsu.com> References: <4C7F446F.8040303@cn.fujitsu.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Thu, 02 Sep 2010 12:38:36 +0200 Message-ID: <1283423916.2059.1847.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2010-09-02 at 14:30 +0800, Li Zefan wrote: > Calling task_subsys_state() without holding rcu_read_lock or > cgroup_mutex can cause lockdep warning. > That is not a suitable changelog. Was the warning correct? Is your patch correct? What does RCU protect here and why can we use classid after dropping it. Simply frobbing code to make the warning go away is not good.